commit | e2e9aa9d2d03077f545c9d088a1f3469d9e28494 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Wed Dec 02 13:26:45 2020 +0100 |
committer | Edwin Kempin <ekempin@google.com> | Mon Dec 14 09:27:49 2020 +0100 |
tree | 384185a17c8e98af12d2aebae8c799b65dc36c94 | |
parent | 3abfd45eb569aa233f57152b95e8831dc0dc4d5a [diff] |
On vote include approved paths into the change message When a code owner votes on the code owner label, include into the change message which files/paths: * are approved now * are no longer approved * are still approved This makes makes the effect on voting on the code owner label more transparent to users. The paths in the change message are absolute file paths. They do not have a leading '/' so that they match the paths in the file list on the change screen which also do not have a leading '/'. Example change message: "By voting Code-Review+1 the following files are now code-owner approved by John Doe: * foo/bar.baz * foo/baz.bar" * foo/bar/baz.foo" Please note that the change message will contain old and new paths, e.g. if a file is renamed, both the old and new path will be included (assuming that they are both owned by the user). In a follow-up change we may also extend the change message if a code owner override is applied. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: Idd11f2ea6021384a92f0a5588088e5cfda20a6c0
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