Resolve "Better documentation on import from GitHub"
What does this MR do?
Resolve remaining issue with #18783 (closed), which was filed in July 2017. The noted doc, https://docs.gitlab.com/ee/user/project/import/github.html#import-your-project-from-github-to-gitlab, has been revised several times since, but I've identified one more issue which can still cause confusion:
GitHub defines the "primary" and "public" email address differently. In fact, the public email address on a GitHub account can differ from the primary address, which is what admins need to import.
Related issues
Closes #18783 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖