Do not run the code owners submit rule for closed changes

Running the code owners submit rule is rather expensive, since we need
to compute the code owner statuses for all files which have been touched
in the change, which requires loading the relevant OWNERS files for each
of the files. Submit rules are also invoked for closed changes (e.g.
each time a change is reindexed), but the code owner status on closed
changes is not relevant, hence we should not compute it.

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