| commit | b56e764ce200c2bd33ebdd1b557982148ab8b68e | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Wed Nov 18 13:39:41 2020 +0100 |
| committer | Edwin Kempin <ekempin@google.com> | Wed Nov 18 13:54:09 2020 +0100 |
| tree | a89f982901dcd629ba4d3225904bab81e42ec591 | |
| parent | dd2fb4e06319e46c10fabd936342ef5afcb131c1 [diff] |
Don't filter out service users when listing code owners for path in branch Currently we have 2 REST endpoints to list code owners for a path that behave the same: * GetCodeOwnersForPathInBranch * GetCodeOwnersForPathInChange Going on GetCodeOwnersForPathInChange will be used to suggest code owners for a path on a change, whereas GetCodeOwnersForPathInBranch lists all code owners for path. The difference is that for GetCodeOwnersForPathInChange we will filter out code owners that should not show up in the suggestion (e.g. service users) whereas GetCodeOwnersForPathInBranch includes all code owners. The frontend part was already adapted to use GetCodeOwnersForPathInChange for suggestion code owners (see change Ie04e60913). GetCodeOwnersForPathInBranch is not used by the frontend, but is intended to be used by bots that want to query all code owners. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: Ifbec40349fa1bde36ea36822e6f4bc2a39fd295e
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