CheckCodeOwner: Inform in debug logs about imported code owner configs

So far the CheckCodeOwner REST endpoint only tells about unresolveable
imports, but not which code owner configs have been imported. Include
this info to make debugging easier.

This also fixes the name of the importing config in messages that inform
about unresolved imports (so far it always used the name of the start
code owner config, even if the unresolveable import appeared in an
imported code owner config).

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: If287594c0be6f66dc1e5496469234bd12bed66d6
7 files changed
tree: 8efde062dcff20bb192d9880e9474f62b3c6a7be
  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