diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 21:09:09 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 21:09:09 +0000 |
| commit | 1902e256266822bc94e1a69debd79fb256de2d79 (patch) | |
| tree | 2a6a431d24bc7c293312cb84bdfad6a438fa4d80 /doc/user/project | |
| parent | f781b0b69368ea3181cf892305c60a22886c0d7e (diff) | |
| download | gitlab-ce-1902e256266822bc94e1a69debd79fb256de2d79.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project')
| -rw-r--r-- | doc/user/project/code_owners.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/user/project/code_owners.md b/doc/user/project/code_owners.md index 45d9e8f04e0..40ea1833fa3 100644 --- a/doc/user/project/code_owners.md +++ b/doc/user/project/code_owners.md @@ -88,6 +88,23 @@ or more users or by the `@name` of one or more groups that should be owners of the file. Groups must be added as [members of the project](members/index.md), or they will be ignored. +Starting in [GitLab 13.0](https://gitlab.com/gitlab-org/gitlab/-/issues/32432), you can now specify +groups or subgroups from the project's group hierarchy as potential code owners. + +For example, consider the following hierarchy for a given project: + +```text +group >> sub-group >> sub-subgroup >> myproject >> file.md +``` + +Any of the following groups would be eligible to be specified as code owners: + +- `@group` +- `@group/sub-group` +- `@group/sub-group/sub-subgroup` + +In addition, any groups that have been invited to the project using the **Settings > Members** tool will also be recognized as eligible code owners. + The order in which the paths are defined is significant: the last pattern that matches a given path will be used to find the code owners. |