Add REST endpoint to validate the code owner config files of a project

This REST endpoint allows project owners to validate the code owner
config files in their projects and fix the detected issues. This is
important since code owner config files can become invalid after they
have been submitted, e.g. because a referenced code owner config file
has been deleted.

No validation is done for branches for which the code owner
functionality is disabled.

In the ProjectCodeOwners API class we have an inner class to represent
the request to check code owner config files so that we can add
parameters for this REST endpoint later without making an incompatible
API change.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I3cfa1b846a6dc223e849b6b9c57a7c9ea03abddc
14 files changed
tree: 42e3842af40b6b5bf606f9a23ddb599f72d848b9
  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