Better documentation on import from GitHub
A customer (https://gitlab.my.salesforce.com/00161000013ZvZ0) needs to import projects from GitHub.com to their GitLab instance and has reported that our docs and the process is not very clear:
if you have a Github repo where 5 developers have made commits, and then 1 of the developers transfer it.
Then he will be the only one who has linked his Github and Gitlab account, which means that for the remaining 4 developers their actions previously done in Github will not be tied with their Gitlab account.
So I wondered if there is a way of connecting your Github account with Gitlab that doesn't involve transferring a project.
This is a quote from the page (https://docs.gitlab.com/ee/workflow/importing/import_projects_from_github.html#how-it-works) I linked: "For this to work, the GitHub author/assignee should have signed in beforehand in GitLab and associated their GitHub account."
@andrewn had to import a project recently and could provide some recommendations: https://gitlab.slack.com/archives/C3W3PSR88/p1500027205598918
- Make sure that every user has a GitLab account
- Make sure that the user’s public email address on the profile on GitHub.com matches an email address registered in your GitLab profile.
It's unclear whether the public GitHub address needs to match the primary GitLab address but it’s important that the public email address on GitHub.com matches the profiles on GitLab for the import process to associate issues etc with the correct user.
@axil The customer is asking for improved documentation or a guide which explains exactly what should be changed where so that their developers know exactly what to do.
@mydigitalself Is it possible to import projects without making email addresses visible outside the organisation?