Count sticky approvals on old patch sets as code owner overrides

If an approval was applied on an old patch set which is still valid for
the current patch set because it is sticky we must consider it as code
owner override the same way as approvals that have been applied on the
current patch set.

The computation of sticky approvals is done by ApprovalInference which
we are now using by retrieving the approvals through ApprovalUtil.

The same issue was already fixed for code owner approvals by change
I2131162f5.

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