Gitea Importer - Map contributions to personal namespace owner
What does this MR do and why?
This MR updates the Gitea importer so that when a project is imported into a personal user namespace, all user contributions are assigned to the personal namespace owner. Because personal namespaces don't have memberships like groups, there's no way for a user to reassign placeholder users via the UI. Plus, user contribution mapping isn't supported in personal namespaces, so it's simpler to immediately map contributions to the namespace owner. Only personal namespace owners and admins can import projects into a personal namespace (see user_namespace_policy)
References
- Related to #525342 (closed)
- Implementation in Bitbucket Server importer: !198010 (merged)
- Implementation in GitHub importer: !198624 (merged)
Screenshots or screen recordings
| Destination type | Before | After |
|---|---|---|
| Personal namespace |  |
user_mapping_to_personal_namespace_owner enabled: user_mapping_to_personal_namespace_owner disabled: 
|
| Group |  |
user_mapping_to_personal_namespace_owner enabled (no effect):
|
How to set up and validate locally
- Enable
user_mapping_to_personal_namespace_owner - Ensure you have access to a Gitea repository with user contributions. See import from Gitea docs for instructions and prerequisites
- Import a repository from Gitea into a personal namespace
- Verify that all user contributions have been mapped to the namespace owner
- Import the project to group
- Verify that placeholder users were created and user mapping is unaffected
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.
Related to #525342 (closed)