Restrict Branch Creation via git push to Specific Roles, While Allowing UI-Based Branch Creation

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Description:

Currently, it is not possible in GitLab to selectively restrict branch creation via git push for specific roles while still allowing branch creation through the GitLab UI. While Push Rules can limit the names of branches created, they do not provide the capability to prevent branch creation altogether via git push or restrict this action to specific roles.

In some workflows, users need to control how branches are created to maintain consistency and security:

Some orgs would like to prevent users with certain roles from creating branches via git push, or ideally restrict this action to specific roles. However, we still want all users to have the option to create branches through the GitLab UI.

Feature Request:

Add a feature to selectively restrict branch creation via git push based on user roles, while allowing unrestricted branch creation through the GitLab UI.

Benefits:

- Enhanced Access Control: Allows teams to enforce branching policies based on roles.
- Improved Workflow Management: Enables administrators to control branch creation methods, maintaining consistency and security.
- Flexibility: Users who are restricted from creating branches via git push can still create branches through the UI, ensuring they are not blocked from necessary workflows.

This feature would greatly benefit organizations seeking more granular control over branch management workflows.