Docs feedback: API documentation for "Update a protected branch" says "allowed_to_merge" and "allowed_to_push" are Premium and Ultimate only

  • Start this issue's title with Docs: or Docs feedback:.

Problem to solve

The section on updating protected branches shows that the allowed_to_merge and allowed_to_push attributes are "Premium and Ultimate only." I believe this is potentially misleading.

Further details

I suspect what this is supposed to indicate is that Premium or Ultimate is required in order to specify groups or users rather than roles, but the documentation doesn't make that distinction entirely clear. I momentarily thought that it meant non-premium users would have to delete the branch protection completely and re-add it if they wanted, for example, to use the API to change from "Only maintainers can push and merge" to "Only maintainers can merge and no one can push."

Note: The descriptions of the attributes in the response only indicate "Premium and Ultimate Only" for .user_id and .group_id and not for .access_level .

Proposal

Change the description in the table somehow to make it clear that the "Premium and Ultimate Only" refers to specifying users. groups, and deploy keys. I'm not sure what would be a good and concise way to do this.

Who can address the issue

Other links/references

Edited Mar 05, 2026 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading