Google Git
Sign in
gerrit / plugins / code-owners / 3b073da71e532a2a2298becf68f4d43b85cc88a8
commit3b073da71e532a2a2298becf68f4d43b85cc88a8[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Fri Mar 12 10:33:45 2021 +0100
committerEdwin Kempin <ekempin@google.com>Fri Mar 12 10:58:28 2021 +0100
treea8a2e13a584c12066d74bc903734a7348f03d6d6
parente4ddca672f051ad3171154ee953653689eb81213 [diff]
Allow validating code owner configs even if code owners is switched off

When rolling out code-owners, it can make sense to enable the validation
of code owner config files before enabling the code owners
functionality. To support this we add 'FORCED' and 'FORCED_DRY_RUN' as
new options for the enableValidationOnCommitReceived and
enableValidationOnSubmit configuration parameters, since 'TRUE' and
'DRY_RUN' only trigger the validation if the code owners functionality
is enabled.

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