Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
c06bc4e3
Commit
c06bc4e3
authored
Sep 04, 2018
by
Achilleas Pipinellis
Committed by
Bob Van Landuyt
Sep 06, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Refactor code owners docs
parent
dbde2b33
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
18 additions
and
15 deletions
+18
-15
doc/user/project/code_owners.md
doc/user/project/code_owners.md
+17
-13
doc/user/project/index.md
doc/user/project/index.md
+1
-2
No files found.
doc/user/project/code_owners.md
View file @
c06bc4e3
# Code owners
> [Introduced][introduced-mr] in [Gitlab Starter][ee] 11.3
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6916)
in
[
Gitlab Starter
](
https://about.gitlab.com/pricing/
)
11.3.
You can use a
`CODEOWNERS`
file to specify users that are responsible
for
a certain part of the code
in a repository.
for
certain files
in a repository.
The codeowners file can be added to the root of the repository, inside
the
`.gitlab/`
or the
`docs/`
folder.
You can choose and add the
`CODEOWNERS`
file in three places:
The
`CODEOWNERS`
is scoped to a branch. This means that with the
introduction of new files, the developer adding the new code can
specify themselves as code owner. Before the new code gets merged to
master.
-
to the root directory of the repository
-
inside the
`.gitlab/`
directory
-
inside the
`docs/`
directory
The
`CODEOWNERS`
file is scoped to a branch, which means that with the
introduction of new files, the person adding the new content can
specify themselves as a code owner, all before the new changes
get merged to the default branch.
When a file matches multiple entries in the
`CODEOWNERS`
file,
the users from all entries are displayed on the blob page of
the given file.
## The syntax of a code owners file
...
...
@@ -53,7 +61,7 @@ CODEOWNERS @multiple @owners @tab-separated
# users. Everything else will be ignored. For example this will
# specify `@legal` and a user with email `janedoe@gitlab.com` as the
# owner for the LICENSE file
LICENSE @legal this
does not
match janedoe@gitlab.com
LICENSE @legal this
_does_not_
match janedoe@gitlab.com
# Ending a path in a `/` will specify the code owners for every file
# nested in that directory, on any level
...
...
@@ -72,10 +80,6 @@ lib/ @lib-owner
# repository
/config/ @config-owner
# If the path contains spaces, these need to be escaped like this:
path\ with\ spaces/ @space-owner
```
[
introduced-mr
]:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6916
[
ee
]:
https://about.gitlab.com/pricing/
doc/user/project/index.md
View file @
c06bc4e3
...
...
@@ -87,8 +87,7 @@ website with GitLab Pages
your code blocks, overriding GitLab's default choice of language
-
[
Badges
](
badges.md
)
: Badges for the project overview
-
[
Maven packages
](
maven_packages.md
)
: Your private Maven repository in GitLab
-
[
Code owners
](
code_owners.md
)
: Specify code owners for certain files
**[STARTER]**
-
[
Code owners
](
code_owners.md
)
: Specify code owners for certain files
**[STARTER]**
### Project's integrations
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment