Show different error message if server config is invalid

If a code-owners operation cannot be performed because the project
contains an invalid OWNERS file the backend returns a '409 Conflict'
response informing about the invalid OWNERS file. An invalid OWNERS file
is a configuration issue that needs to be fixed by the project owner or
host admin, it's not an error in the code-owners plugin (an error would
be signaled as 500 response). At the moment the frontend reports invalid
OWNERS file as a red error banner. This gives the wrong impression that
there was an error in the code-owners plugin. The way how invalid OWNERS
files are reported/shown to the user is changed so that it's more clear
that this is a configuration issue and not an error in the plugin.

Change-Id: I0e2524cbd1c76f954b77aff19a0da06b78574aec
5 files changed
tree: a0a641d1c777517024ab43ec66f0eab5d9849c76
  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.