Allow to define and configure override label in the same commit

When a code-owners.config file is pushed we validate the override
configuration in it. This includes checking if the configured label
exists for the project. If the label didn't exist yet, but was
configured in the commit that is being pushed, we didn't take it into
account and wrongly rejected the commit, saying that the label doesn't
exist (because we read the labels from the head revision of
refs/meta/config and not from the commit that was being pushed). This is
fixed now, by reading the available labels from the commit that is being
pushed.

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