Commit 27a4a9d9 authored by Patrick Bajao's avatar Patrick Bajao

Clarify requirements to create protected branches

Add information about only being able to create a
protected branch if user is also allowed to merge.
parent def19634
...@@ -118,10 +118,11 @@ all matching branches: ...@@ -118,10 +118,11 @@ all matching branches:
When a protected branch or wildcard protected branches are set to When a protected branch or wildcard protected branches are set to
[**No one** is **Allowed to push**](#using-the-allowed-to-merge-and-allowed-to-push-settings), [**No one** is **Allowed to push**](#using-the-allowed-to-merge-and-allowed-to-push-settings),
Developers (and users with higher [permission levels](../permissions.md)) are allowed Developers (and users with higher [permission levels](../permissions.md)) are
to create a new protected branch, but only via the UI or through the API (to avoid allowed to create a new protected branch as long as they are
creating protected branches accidentally from the command line or from a Git [**Allowed to merge**](#using-the-allowed-to-merge-and-allowed-to-push-settings).
client application). This can only be done via the UI or through the API (to avoid creating protected
branches accidentally from the command line or from a Git client application).
To create a new branch through the user interface: To create a new branch through the user interface:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment