CodeOwnerApprovalCheck: Avoid passing implicit approval flag into all methods

This was a bit confusing:

* if enableImplicitApprovalFromUploader == true, then patchSetUploader
  was guaranteed to be non-null
* if enableImplicitApprovalFromUploader == false, then patchSetUploader
  could have been null (e.g. for calls done from
  getFileStatusesForAccount(...))

Instead of passing in enableImplicitApprovalFromUploader and the
patchSetUploader, just pass in a nullable implicitApprover (account ID
of the implicit approver). If implicitApprover is set, there is an
implicit approval from that account. If implicitApprover is not set
there is no implicit approval. That's easier to understand.

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