| commit | 5e3d038e6021f1b7463247846d5f77555dd7809e | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Wed Oct 21 10:35:02 2020 +0200 |
| committer | Edwin Kempin <ekempin@google.com> | Fri Oct 23 10:36:38 2020 +0200 |
| tree | eae0d8e1059eadf8953e05e042e67e6b842e4bee | |
| parent | fbb5c8d014de7ef307f22e45937cd8ce03b51eba [diff] |
Report parsing errors as fatal Parsing errors are worse then other errors since non-parseable code owner config files can make changes non-submittable, while other errors just lead to ignoring that part of the config. In a follow-up change we want to extend the check code owner config REST endpoints to accept a verbosity level as input that controls which kind of issues should be reported. For example, by setting the verbosity level to fatal one can then 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. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: Ief72e334c6234e7652d9cdc859550bacacce2ad0
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