Revert "No default selection of destination namespace when importing with GH, BB ad Gitea"
What does this MR do and why?
This reverts merge request !190598 (merged) due to import errors observed in production.
In removing the default target namespace as called for in the original issue, there'd need to be additional validation preventing the frontend from sending an import request for multiple projects when one or more of the projects do not have a destination namespace selected. The MR to be reverted only fixed single-project imports.
See bug report in #545962 (comment 2528828290) . It needs to be more clear to the user that they have to choose a namespace for each repo if importing several repos at a time. We might also want to confirm whether this is the ideal UX. In the interim, we should revert the MR as customers are seeing errors while importing as a result of that change.
References
Purpose of revert
Checklist
-
Create an issue to reinstate the merge request and assign it to the author of the reverted merge request. -
If the revert is to resolve a broken 'master' incident, please read through the Responsibilities of the Broken masterresolution DRI. -
If the revert involves a database migration, please read through Deleting existing migrations. -
Add the appropriate labels before the MR is created. We can skip CI/CD jobs only if the labels are added before the CI/CD pipeline is created.
Milestone info
-
I am reverting something in the current milestone. No changelog is needed, and I've added a ~"regression:*"label. -
I am reverting something in a different milestone. A changelog is needed, and I've removed the ~"regression:*"label.
Screenshots or screen recordings
This returns the github / gitea / bitbucket importer to the state prior to the recent merge.
How to set up and validate locally
- Go through the flow of importing a project from Github
- try to import multiple repos by clicking Import 23 repositories
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.