commit b05b2876365d6bb60dae7fda170a31fe36682616
author Edwin Kempin <ekempin@google.com> Fri Oct 02 12:20:36 2020 +0200
committer Edwin Kempin <ekempin@google.com> Tue Oct 06 14:31:52 2020 +0200
tree 626fe16c1c7a5aafab6ad157a01069c111d0d748
parent ec97c14717ec57ff18ccc1223aa048d50287e721

Support to validate the code owner config files in a revision/patch set

This allows to validate the code owner config files in open changes. The
validation is performed from the perspective of the uploader, so that
the validation is exactly the same as the validation that will be done
on submit.

At the moment this REST endpoint doesn't provide much value since code
owner config files are already validated on push and the upload is
rejected if the commit contains invalid code owner config files. So in
practice changes should not contain invalid code owner config files.
However in future we want to allow project owners to switch off the
validation on upload and instead run a bot that does the validation on
the open changes as a pre-submit check. In this case the bot would use
this REST endpoint to do the validation on the open changes.

The REST endpoint also works if the code owners functionality of the
destination branch is disabled. This is consistent with our general
strategy to keep all code owner REST endpoints fully working even if the
code owners functionality is disabled. In addition it also matches the
user expectation. If the user asks us to run the validation for a
particular change/patch set we should just do it, even if the code
owners functionality is disabled for the destination branch.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I010fbc9804bf14a418572234626c5a69e75840f1