Wrong commit email in GitHub import projects
Summary
During the import process of a project from GitHub to GitLab, there is an issue with the usage of GitHub-generated email IDs and the addition of an "unverified" label on the PR merge commits. This behavior results in incorrect email IDs being associated with the commits and the unverified label misleadingly applied to the imported data.
Steps to reproduce
- In GitHub use Github AutoMerge feature https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
- Perform a project import from GitHub to GitLab.
- Observe the imported PR merge commits.
- Check the email IDs associated with the users who made the PR merge commits.
- Notice that the GitHub-generated email IDs are used instead of the users' public email IDs.
- Verify the presence of the "unverified" label on the PR merge commit entries.
Example Project
What is the current bug behavior?
The import process uses GitHub-generated email IDs instead of the public email IDs of the users for PR merge commits. Additionally, an "unverified" label is wrongly added to the PR merge commit entries, even though there may not be any verification issue with the email IDs.
What is the expected correct behavior?
During the import of a project from GitHub, the PR merge commits should correctly use the public email IDs of the users involved. The imported data should not have an "unverified" label attached to the PR merge commit entries.
Relevant logs and/or screenshots
Output of checks
Possible fixes
None at the moment.