commit | 3d006a10b05565a2927167ed10cb3157bfb03be3 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Mon Dec 28 11:55:23 2020 +0100 |
committer | Edwin Kempin <ekempin@google.com> | Thu Jan 07 09:52:10 2021 +0100 |
tree | 7568f1598d6d6370ab7547a4e46bb21697ed9004 | |
parent | 3b7950f44f23d43da790b350a738ea9567997954 [diff] |
Count sticky approvals on old patch sets as code owner overrides If an approval was applied on an old patch set which is still valid for the current patch set because it is sticky we must consider it as code owner override the same way as approvals that have been applied on the current patch set. The computation of sticky approvals is done by ApprovalInference which we are now using by retrieving the approvals through ApprovalUtil. The same issue was already fixed for code owner approvals by change I2131162f5. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: Ifb7921336187c4b6d867ebe3397c9e1eed1d812d
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