Fix gitlab:import:repos Rake task moving repositories into the wrong location

If the source import directory were different from the destination directory, GitLab would first create a blank repository and then erroneously move the original one into a subdirectory. Adding an import type prevents this the project from being initialized in the first place. It was accidentally removed in 1f917cbd.

Closes #40765 (closed)

added 207 commits

• 234bdfd6...806a68a8 - 206 commits from branch master
• 78f7c3c8 - Fix gitlab:import:repos Rake task moving repositories into the wrong location

Compare with previous version

added 1 commit

• e8cced80 - Fix failing importer test case on MySQL due to missing trailing slash in root path

Compare with previous version

Thanks Stan!

assigned to @stanhu

added 1 commit

• 917a112e - Simplify normalizing of paths

Compare with previous version

added 1 commit

• 86661a3a - Use build instead of create in importer spec

Compare with previous version

resolved all discussions

added 1 commit

• f1eaab7b - Remove the need for destroy and add a comment in the spec

Compare with previous version

assigned to @jameslopez

approved this merge request

enabled an automatic merge when the pipeline for f1eaab7b succeeds

Thanks @stanhu - LGTM!

I think we can merge this :)

merged

mentioned in commit 7694ae88

mentioned in commit 0f04fa28

Picked into https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15907, will merge into 10-3-stable ready for 10.3 RC1.

mentioned in commit d463c6a9

Picked into https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15925, will merge into 10-2-stable ready for 10.2.5

/cc @mkozono

mentioned in issue #41149 (closed)

mentioned in issue #41424 (closed)

mentioned in merge request !16115 (merged)