Google Git
Sign in
gerrit / plugins / code-owners / 359048b030c83b9a1e61a78ee992817199c089df
commit359048b030c83b9a1e61a78ee992817199c089df[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Wed Jan 27 10:33:03 2021 +0100
committerEdwin Kempin <ekempin@google.com>Wed Jan 27 10:38:13 2021 +0100
tree2582505e887649dea046d777c0f4b020d363067f
parentde7b8bb3c5377042685f7e607477ccea03aad089 [diff]
Allow to set fallback code owners for a project via REST

Being able to set fallback code owners via REST is more comfortable than
editing the code-owners.config manually.

Setting fallback code owners should be more comfortable since it needs
to be done frequently when the code owners functionality is rolled out
to projects, e.g. a common rollout strategy is:

1. enable the code owners functionality with all users as fallback code
   owners
2. start adding OWNERS files
3. remove all users as fallback code owners and rely on the OWNERS files
   only

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Iff8d0cf4f2753279f8b45c2d1317a7870b42c5cb
4 files changed
tree: 2582505e887649dea046d777c0f4b020d363067f
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md