Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorIgor <idrozdov@gitlab.com>2019-07-04 12:13:50 +0300
committerDouwe Maan <douwe@gitlab.com>2019-07-04 12:13:50 +0300
commitae7041d4dae5650172858ec86bcb6ca92ec4512a (patch)
tree2065d0ad82f77585295a1749dcfe49f977ea14b8 /doc
parent97b2a3cc7c3fab546c60229c9d058fa1472724ac (diff)
Backports for EE's "Allow adding groups to CODEOWNERS file"
Some general code has been added/removed in EE version which needs to be backported in CE
Diffstat (limited to 'doc')
-rw-r--r--doc/user/project/code_owners.md15
1 files changed, 11 insertions, 4 deletions
diff --git a/doc/user/project/code_owners.md b/doc/user/project/code_owners.md
index ae04616943f..c76847616b3 100644
--- a/doc/user/project/code_owners.md
+++ b/doc/user/project/code_owners.md
@@ -1,10 +1,12 @@
# Code Owners **[STARTER]**
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6916)
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6916)
in [GitLab Starter](https://about.gitlab.com/pricing/) 11.3.
+> - [Support for group namespaces](https://gitlab.com/gitlab-org/gitlab-ce/issues/53182) added in GitLab Starter 12.1.
-You can use a `CODEOWNERS` file to specify users that are responsible
-for certain files in a repository.
+You can use a `CODEOWNERS` file to specify users or
+[shared groups](members/share_project_with_groups.md)
+that are responsible for certain files in a repository.
You can choose and add the `CODEOWNERS` file in three places:
@@ -25,7 +27,8 @@ the given file.
Files can be specified using the same kind of patterns you would use
in the `.gitignore` file followed by the `@username` or email of one
-or more users that should be owners of the file.
+or more users or by the `@name` of one or more groups that should
+be owners of the file.
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
@@ -63,6 +66,10 @@ CODEOWNERS @multiple @owners @tab-separated
# owner for the LICENSE file
LICENSE @legal this_does_not_match janedoe@gitlab.com
+# Group names can be used to match groups and nested groups to specify
+# them as owners for a file
+README @group @group/with-nested/subgroup
+
# Ending a path in a `/` will specify the code owners for every file
# nested in that directory, on any level
/docs/ @all-docs