Allow to enable/disable the code owners functionality via REST

So far enabling/disabling the code owners functionality required
fetching refs/meta/config, editing the code-owners.config file and
pushing back the updates to refs/meta/config. Using a REST endpoint for
this is more comfortable since it is a single command.

When starting to use code-owners, project owners may want to
enable/disable the code owners functionality a few times until all is
properly setup. Hence we want to make this easier for them.

Follow-up changes may extend the new REST endpoint to allow updating
further configuration parameters.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I395fc2faebfd316bc85a4ba7c616190f4a7252f9
19 files changed
tree: 5ba9d1680806feacfbe87ebe85b88337b4b1b5f8
  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