Create a protected branches API
Description
- Currently, the only way to protect/unprotect a branch via the API is to use the
branchesAPI - The
branchesAPI does not mirror the internal data model for protected branches - this can't be changed due to backward compatibility - This causes a number of edge cases in the code that glues these two data models together
Proposal
- Create a new "protected_branches" API that allows performing CRUD actions directly on protected branches, rather than operating on git branches
- The API should allow performing all actions that are currently possible through the web interface:
- Create a wildcard protected branch
- Set the "Allowed to push" setting to "Developers", "No one", or "Developers + Masters"
- Set the "Allowed to push" setting to any combination of the above, in addition to specific users and groups (EE-only)
- Set the "Allowed to merge" setting to "Developers" or "Developers + Masters"
- Set the "Allowed to merge" setting to any combination of the above, in addition to specific users and groups (EE-only)
Links / references
Issues that can be closed once this API is implemented: #30009 (moved), #27371 (moved), #22317 (moved), #20369 (moved), #27062 (moved)
Activity
@mydigitalself: Could you please prioritise this issue?
mentioned in issue #27062 (moved)
added repository label
mentioned in issue #30009 (moved)
mentioned in merge request !10356 (merged)
@timothyandrew Once this new API has been designed, it should also be used to implement an API for Protected Tags
mentioned in issue #31100 (closed)
mentioned in merge request !12756 (merged)
added Community Contribution label
assigned to @godfat
marked this issue as related to #27371 (moved)
mentioned in issue #35867 (moved)
Most parts were implemented, therefore splitting to https://gitlab.com/gitlab-org/gitlab-ce/issues/35867
changed milestone to %9.5
marked this issue as related to #35867 (moved)
