Set protected branches "Allowed to push" to "No one" via API

Description

It is currently only possible to set the "Allowed to push" (or merge) properties of a protected branch to either "Master" or "Developers + Masters" via the API (using the developers_can_push property of the "Protect repository branch" endpoint).

However, we would like to set it to "No one" (we have some branches which must only be modified via a MR).

Proposal

To keep the API similar to the protect branches UI, I'd propose replacing the current developers_can_push = boolean property with an allowed_to_push = 'no one' | 'masters' | 'developers+masters'. The same should be done to replace the developers_can_merge parameter.

Links / references

• Protect repository branch API endpoint

mentioned in issue gitlab-foss#27062 (moved)

I need this too, not sure why they can't even put in a boolean to do masters_can_push=false

added 480950 13884 gitlab-foss14213 gitlab-foss155949 labels

mentioned in issue gitlab-foss#29272 (moved)

mentioned in issue gitlab-foss#30102 (closed)

Related to gitlab-foss#2456 (moved).

Bump, we need this

It would be useful if these endpoints accepted user IDs also, though that might be a separate feature request :)

Bump, we need this

I just spoke with EEP customer that would like this feature.

EEP Customer: https://na34.salesforce.com/0016100000W3J3M

added customer+ in GitLab FOSS label

changed milestone to %Backlog in gitlab-foss

@mydigitalself see request of customer.

@JobV Is this feature available in 9.3.6? If available means how can I protect the branch by no one via API?

changed milestone to %Next 2-3 months in gitlab-foss

@arunkumar.nagarajan this feature doesn't exist yet, it is something we will try to address in the near future.

This feature is actually coming soon as part of a Community Contribution in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12756

marked this issue as related to gitlab-foss#30102 (closed)

marked this issue as related to gitlab-foss#27371 (moved)

marked this issue as related to gitlab-foss#27371 (moved)

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12756 implemented that the access level could be set as one of the following:

• No one
• Developer (= developer + master)
• Master (= master only)

However you could only create, delete, but not update at the moment. In order to update, you'll need to delete first, then create.

Does this mean we implement the feature?

marked this issue as related to gitlab-foss#35867 (moved)

I created an updating API part in https://gitlab.com/gitlab-org/gitlab-ce/issues/35867

moved from gitlab-foss#27371 (moved)