Merge changes Ie5b99c2a,I0746546c,I40349324,Idf584990,If008a747, ...

* changes:
  config-faqs: Explain how to define default code owners
  Add metric to count submit rule errors
  config.md: Fix bad link
  CodeOwnerSubmitRule: Report metric for invalid OWNERS files
  Improve error message if CodeOwnerSubmitRule fails due invalid OWNERS file
  Move getParsingErrorMessage method up to test base class
  Test that CodeOwnerSubmitRule returns rule error if OWNERS file is invalid
  Fix names of code owner metrics
  Fix counting submit rule runs as metric
  Move method to get code owner config file name up to base test class
  Add metric that counts how often invalid OWNERS files cause failures
  Allow to configure an info URL that is shown if an OWNERS file is invalid
  GeneralConfig: Factor out a method to read a string value
  GeneralConfig: Fix variable name
  Add specific exception to signal invalid code owner config files
  CheckCodeOwner: Handle files owned by all users
  Config doc: Clarify that this is not the config that defines code owners
  Document that keeping the global config in All-Projects may be dangerous
  User guide: Make clear that label functions are orthogonal to code owners
  User guide: Explain when code owner submit records in the index get stale
  User guide: Add section about code owners submit rule
  Disallow projects to override inherited list configuration parameters
tree: 89d6767dee11cadda981e3af065f934d9c4dcb78
  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.