Allow CSV file to be used to map users when importing from GitHub to GitLab, rather than requiring public GitHub email
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
When importing projects from GitHub to GitLab for users to mapped correctly there are prerequisites that require each user to have a public GitHub email address:
Each GitHub author and assignee in the repository must have a public-facing email address on GitHub that matches their GitLab email address (regardless of how the account was created). If their email address from GitHub is set as their secondary email address in GitLab, they must confirm it.
When issues and pull requests are being imported, the importer attempts to find their GitHub authors and assignees in the database of the GitLab instance. Pull requests are called merge requests in GitLab. For the importer to succeed, matching email addresses are required.
GitHub accounts must have a GitHub public-facing email address so that all comments and contributions can be properly mapped to the same user in GitLab. GitHub Enterprise does not require this field to be populated so you might have to add it on existing accounts.
It would be very helpful if there was an alternative user mapping method supported where a CSV file could be supplied listing GitHub email addresses and their corresponding GitLab email addresses, which the importer would use instead of the current method to map users.
This would avoid the need for multiple GitHub user accounts to be updated to allow a project to be migrated with accurate user attribution details.
This approach has been previously suggested in an older issue.
This issue arose from a customer support ticket (ZD internal link) where it is going to be necessary for 60+ developers to update their GitHub accounts before projects can be imported into GitLab.