Add a debug option for the list code owners REST endpoints

Users frequently ask why a user is or isn't suggested as a code owner.
The new debug option on the list code owners REST endpoint includes
debug logs into the response that help to answer exactly this question.

We already have the CheckCodeOwner REST endpoint which exposes similar
debug logs, but only for a single user. With the new option this
information can be retrieved for all relevant users at once.

Since debug logs may contain sensitive information this option is only
available for users that have the 'Check Code Owner' global capability,
which is also required by the CheckCodeOwner REST endpoint.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I183907365dab02732ff67732a9d09ae95eb10459
12 files changed
tree: 4584a36a00f024bb4f6eca4a7e8855eaa1b38a5f
  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.