Commit f7d5e08e authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'docs-expand-public-email-info' into 'master'

Add info about public email usage for export

See merge request gitlab-org/gitlab!75491
parents 6361a40d f0b90b00
...@@ -44,8 +44,9 @@ Note the following: ...@@ -44,8 +44,9 @@ Note the following:
a maintainer or administrator role in the group where the exported project lives. a maintainer or administrator role in the group where the exported project lives.
- Project members with the [Owner role](../../permissions.md) are imported as Maintainers. - Project members with the [Owner role](../../permissions.md) are imported as Maintainers.
- Imported users can be mapped by their public email on self-managed instances, if an administrative user (not an owner) does the import. - Imported users can be mapped by their public email on self-managed instances, if an administrative user (not an owner) does the import.
Additionally, the user must be an existing member of the namespace, or the user can be added as a The public email is not set by default. Users must [set it in their profiles](../../profile/index.md#set-your-public-email)
member of the project for contributions to be mapped. for mapping to work correctly. Additionally, the user must be an existing member of the namespace,
or the user can be added as a member of the project for contributions to be mapped.
Otherwise, a supplementary comment is left to mention that the original author and Otherwise, a supplementary comment is left to mention that the original author and
the MRs, notes, or issues are owned by the importer. the MRs, notes, or issues are owned by the importer.
- For project migration imports performed over GitLab.com Groups, preserving author information is - For project migration imports performed over GitLab.com Groups, preserving author information is
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment