diff options
| author | Emmanuele Bassi <ebassi@gnome.org> | 2018-04-16 09:41:24 +0100 |
|---|---|---|
| committer | Emmanuele Bassi <ebassi@gnome.org> | 2018-04-16 16:06:33 +0100 |
| commit | 0b4bfd5c935a1a35893dfb71c4044fded4ba9100 (patch) | |
| tree | 5119d3b9ab404223e56007bc13440b25424db3c3 /CONTRIBUTING.md | |
| parent | d79f1fdbce094ca38adff24bd8c3bbd6ee268503 (diff) | |
| download | gtk+-0b4bfd5c935a1a35893dfb71c4044fded4ba9100.tar.gz | |
docs: Start defining the owners of code sectionscode-owners
When filing a new merge request it's often hard to know who to ask for a
review; using the Git log doesn't always help — the person that touched
a file last may just be fixing the build or a compiler warning.
The `CODE-OWNERS` file format is something that GitHub uses in order to
pre-fill the list of reviewers:
https://help.github.com/articles/about-codeowners/
Ideally, in the future, we'll be able to use this file with a bot like
homu to automatically go through newly filed merge requests and
automatically ask the relevant people for reviews, instead of doing this
manually.
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index af38fda299..318c1ce68e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -60,4 +60,6 @@ $ git checkout -b your-branch Once you've finished working on the bug fix or feature, push the branch to the Git repository and open a new merge request, to let the GTK -maintainers review your contribution. +maintainers review your contribution. The [CODE-OWNERS](./docs-CODE-OWNERS) +document contains the list of core contributors to GTK and the areas for +which they are responsible. |