kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Merge branch 'update-doc-for-user-group-project-transfers' into 'master' 

Clarifies documentation for user, group & project transfers

See merge request gitlab-org/gitlab-ce!15896
This commit is contained in:
Douwe Maan 2017-12-14 09:18:04 +00:00
parent 9daeccfb3a 1bdbff2d6d
commit af110b8997
3 changed files with 15 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/user/group/index.md
View File

@ -197,11 +197,11 @@ username, you can create a new group and transfer projects to it.
Changing a group's path can have unintended side effects. Changing a group's path can have unintended side effects.
* Existing web URLs for the group and anything under it (i.e. projects) will * Existing web URLs for the group and anything under it (i.e. projects) will
redirect to the new URLs redirect to the new URLs.
* Existing Git remote URLs for projects under the group will no longer work, but * Existing Git remote URLs for projects under the group will redirect to the new remote URL, and they
Git responses will show an error with the new remote URL will show a warning with the new remote URL.
* The original namespace can be claimed again by any group or user, which will * The redirect to the new URL is permanent, that implies the original namespace
destroy web redirects and Git remote warnings can't be claimed again by any group or user.
* If you are vacating the path so it can be claimed by another group or user, * If you are vacating the path so it can be claimed by another group or user,
you may need to rename the group name as well since both names and paths must be you may need to rename the group name as well since both names and paths must be
unique unique

9
doc/user/profile/index.md
View File

@ -45,11 +45,10 @@ Alternatively, you can follow [this detailed procedure from the GitLab Team Hand
Changing your username can have unintended side effects. Changing your username can have unintended side effects.
* Existing web URLs for the user and anything under it (i.e. projects) will * Existing web URLs for the user and anything under it (i.e. projects) will
redirect to the new URLs redirect to the new URLs.
* Existing Git remote URLs for projects under the user will no longer work, but * Existing Git remote URLs for projects under the user will redirect to the new remote URL. Git responses
Git responses will show an error with the new remote URL will show a warning with the new remote URL.
* The original namespace can be claimed again by any group or user, which will * The redirect to the new URL is permanent, that implies the original namespace can't be claimed again by any group or user.
destroy any web redirects and Git remote warnings
> It is currently not possible to rename a namespace if it contains a > It is currently not possible to rename a namespace if it contains a
project with container registry tags, because the project cannot be moved. project with container registry tags, because the project cannot be moved.

6
doc/user/project/settings/index.md
View File

@ -50,3 +50,9 @@ Here you can run housekeeping, archive, rename, transfer, or remove a project.
It's possible to mark a project as archived via the Project Settings. An archived project will be hidden by default in the project listings. It's possible to mark a project as archived via the Project Settings. An archived project will be hidden by default in the project listings.
An archived project can be fully restored and will therefore retain it's repository and all associated resources whilst in an archived state. An archived project can be fully restored and will therefore retain it's repository and all associated resources whilst in an archived state.
#### Renaming a project
>**Note:** Only Project Owners and Admin users have the permission to rename a project
It's possible to rename a project from "Rename repository" or "Transfer project" sections. When doing so, you will need to update your local repositories to point to the new location, otherwise Git operations will be rejected.