Config guide: Explain the different levels where code owners can be defined

It's difficult to understand when normal code owners should be used vs.
default code owners vs. global code owners vs. fallback code owners.
Provide some overview and recommendations about this.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I860aa7e0117e169fe685ec2bce23d2fc6b865e5a
1 file changed
tree: 5033caa175dcbf87e3f12b3c56b1e7b27843af2f
  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