commit | f730a254e101307b196c81b12c2861213237a4ae | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Mon Apr 12 14:18:35 2021 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Mon May 03 13:32:46 2021 +0000 |
tree | bf0d8a26c9c01707c80b3f913780b289fbaf0a7f | |
parent | a7e4598117df9485c1f6c69099400f83acc1ed8e [diff] |
GetCodeOwnerStatus: Allow to limit the number of returned statuses Computing all code owner statuses can be expensive for large changes. Often callers do not need all code owner statuses, hence it should be possible to limit the result. E.g. the frontend uses this REST endpoint to show the code owner statuses in the file list on the change screen, but for large changes the frontend is not showing all files by default, hence retrieving all code owner statuses in this case would be wasteful. By default the change screen is showing at most 200 files and if the user wants to see more/all files they need to expand the file list. The frontend can set the limit for code owner statuses to 200 now so that these 200 files can be covered (renames are reported as a single code owner status, hence also 200 renames are covered). The start parameter allows to skip file code owner statuses and can be used to paginate over the code owner statuses. When the user expands the file list on the change screen to all files the frontend can use the start parameter to skip the 200 code owner statuses that it already has. Change-Id: I80acb3d1ea04d13db72700623c72dd8c4bf5f63a Signed-off-by: Edwin Kempin <ekempin@google.com>
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.