| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
| |
Like CHANGES, and the test-suite folder, this file receives too many
updates to have a code owner. It is the job of the reviewer of the PR
to review changes to these files as well.
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
| |
Guillaume and I agreed to switch, as the new Sphinx infrastructure
changes this component significantly.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We make GitHub assign only principal maintainers as reviewers. This
reduces the level of noise (PRs with 10 code owners), and makes it easy
for the assignee to check if all reviews have been completed (all
reviewers in the list have to approve the PR, which was not the case
before if two reviewers were assigned for the same component).
This change means that when a principal maintainer submits a patch
touching the component they own, they should ask a review from the
secondary maintainer.
|
| |
|
|
|
|
|
| |
See https://help.github.com/articles/about-codeowners/ for
documentation.
|
|
|
|
| |
Was actually pointing to https://github.com/CHANGES.
|
| |
|
|
The overall goal is to reduce the number of files at the root of the repository.
|