From f38adfd839b79f22a57657d938306e202c013ed9 Mon Sep 17 00:00:00 2001 From: Evan Read Date: Mon, 11 Mar 2019 10:44:09 +1000 Subject: [PATCH 1/2] Improve precision of group docs --- doc/user/group/index.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/doc/user/group/index.md b/doc/user/group/index.md index db576dd5f2321e..5d9fe4f6eb320f 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -205,20 +205,21 @@ Get an overview of the vulnerabilities of all the projects in a group and its su > Introduced in [GitLab Ultimate][ee] 11.9 behind the `insights` feature flag. -## Transfer groups to another group +## Transferring groups -From 10.5 there are two different ways to transfer a group: +From GitLab 10.5, groups can be transfered in the following ways: -- Either by transferring a group into another group (making it a subgroup of that group). -- Or by converting a subgroup into a root group (a group with no parent). +- Parentless groups can be transfered to a group, converting it into a subgroup. +- Subgroups can be transfered to a new parent group. +- Subgroups can be transfered out from a parent group, converting it into a parentless group. -Please make sure to understand that: +When transferring groups, note: -- Changing a group's parent can have unintended side effects. See [Redirects when changing repository paths](https://docs.gitlab.com/ce/user/project/index.html#redirects-when-changing-repository-paths) -- You can only transfer the group to a group you manage. +- Changing a group's parent can have unintended side effects. See [Redirects when changing repository paths](../project/index.md#redirects-when-changing-repository-paths). +- You can only transfer groups to groups you manage. - You will need to update your local repositories to point to the new location. -- If the parent group's visibility is lower than the group current visibility, visibility levels for subgroups and projects will be changed to match the new parent group's visibility. -- Only explicit group membership is transferred, not the inherited membership. If this would leave the group without an owner, the transferring user is added as owner instead. +- If the parent group's visibility is lower than the group's current visibility, visibility levels for subgroups and projects will be changed to match the new parent group's visibility. +- Only explicit group membership is transferred, not inherited membership. If the group's owners have only inherited membership, this would leave the group without an owner. In this case, the user transferring the group becomes the group's owner. ## Group settings -- GitLab From 3003f867827c7672f5094cfe0fb6a11932b6cc03 Mon Sep 17 00:00:00 2001 From: Evan Read Date: Wed, 13 Mar 2019 16:05:21 +1000 Subject: [PATCH 2/2] Implement review comments --- doc/user/group/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 5d9fe4f6eb320f..9b58483af2fa0e 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -207,11 +207,11 @@ Get an overview of the vulnerabilities of all the projects in a group and its su ## Transferring groups -From GitLab 10.5, groups can be transfered in the following ways: +From GitLab 10.5, groups can be transferred in the following ways: -- Parentless groups can be transfered to a group, converting it into a subgroup. -- Subgroups can be transfered to a new parent group. -- Subgroups can be transfered out from a parent group, converting it into a parentless group. +- Top-level groups can be transferred to a group, converting them into subgroups. +- Subgroups can be transferred to a new parent group. +- Subgroups can be transferred out from a parent group, converting them into top-level groups. When transferring groups, note: -- GitLab