| commit | 9d13428223391e6b40e264a72dcb6225a16b33d4 | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Tue Jun 15 12:27:43 2021 +0200 |
| committer | Edwin Kempin <ekempin@google.com> | Tue Jun 15 15:02:39 2021 +0200 |
| tree | 1d78b0029fb8bcd74d01c0945edf000c3e2745c0 | |
| parent | 0be91190714fa0a3e82f5202c25e2a1da112b31c [diff] |
Test skipping code owner config validation when creating merge via API If a change for a merge commit is created via the Create Change REST endpoint the code owner config file validation validates any OWNERS file that is touched in the merge commit. This validation fails if such an OWNERS file contains conflicts (conflicts are possible if mergeInput.allowConflicts = true was set), since the conflict markers in the file will be detected as invalid content. Change I936a8b6d6 in Gerrit core allows to set validation options in the change input that are forwarded to the CommitValidationListeners. This makes it possible to skip the code owner config validation when creating a change via the Create Change REST endpoint, by specifying code-owners~skip-validation=true as validation option. This change adds a test to verify that skipping the code owner config validation by setting code-owners~skip-validation=true in change input works. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: Ib9eb5182cf0aabfc07b61a72ba95edf259222de3
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.