| commit | 82d007993385836c756b79cb49a8e20400cb58dd | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Wed Oct 21 12:29:25 2020 +0200 |
| committer | Edwin Kempin <ekempin@google.com> | Fri Oct 23 10:36:49 2020 +0200 |
| tree | 587899cd0b6793034462c018a7acb914098be441 | |
| parent | 5e3d038e6021f1b7463247846d5f77555dd7809e [diff] |
Allow to set a verbosity level on check code owner config REST endpoints The check code owner config REST endpoints accept a verbosity level as input now that controls which kind of issues should be reported. For example, by setting the verbosity level to fatal one can use these REST endpoint to only check for non-parseable code owner config files, without needing to filter out other results manually. E.g. checking for non-parseable code owner config files should be done before turning on the code owners functionality for a project. Change-Id: I29f301afd7a21815f00a1191bacd385caeb25631 Signed-off-by: Edwin Kempin <ekempin@google.com>
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