Document that code owner approvals always apply to all files in the change

Code owners may be tempted to review only the files that they own, but
this is not recommended since their approval counts for all files in the
change (as voting is done on change level, not on file level). E.g. this
is a problem if:

* a change touches files A and B
* a user owns file A, but not file B
* the user reviews only file A and approves the change
* the OWNERS files are changed so that the user owns file B too now
* the approval that was given by the user on the change approves files A
  and B now, but the user actually didn't review file B

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