| commit | 764adb2f93b711f63af21a79d5486c42880341df | [log] [tgz] |
|---|---|---|
| author | Dmitrii Filippov <dmfilippov@google.com> | Fri Nov 06 10:14:30 2020 +0100 |
| committer | Dmitrii Filippov <dmfilippov@google.com> | Fri Nov 06 09:16:47 2020 +0000 |
| tree | fc51007d426854b71a2811a128a31e509c04b2c5 | |
| parent | 6d904f0fc92e5adda55417047a9fec41e5a6222b [diff] |
Use new Get Code Owner Branch Config REST endpoint in frontend At the moment the code-owners frontend is using the Get Code Owner Project Config REST endpoint to read the plugin configuration and to decide whether the code owner UI controls should be shown. It turned out the this REST endpoint is too slow if a repository contains many branches, as it returns some information (whether the code owners functionality is enabled/disabled and which code owner backends is used) for every branch. Computing this information for all branches is unnecessary as the frontend is only interested in the information about the target branch of the change. Change-Id: I357f0664fcfb0a06a690312766e7fe057873a348
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