Commit 2adf3fe8 authored by Marcin Sedlak-Jakubowski's avatar Marcin Sedlak-Jakubowski

Merge branch...

Merge branch 'spagert/gitlab-add-note_documentation-protected-branches_initial-push-as-developer' into 'master'

Docs: coach-will-finish note about main branch in protected branches

See merge request gitlab-org/gitlab!53031
parents f8f541b5 e089042f
...@@ -21,13 +21,17 @@ By default, a protected branch does these things: ...@@ -21,13 +21,17 @@ By default, a protected branch does these things:
- It prevents **anyone** from force pushing to the branch. - It prevents **anyone** from force pushing to the branch.
- It prevents **anyone** from deleting the branch. - It prevents **anyone** from deleting the branch.
NOTE: **Permissions:**
A GitLab administrator is allowed to push to the protected branches.
See the [Changelog](#changelog) section for changes over time. - GitLab administrators are allowed to push to the protected branches.
- Users with [Developer permissions](../permissions.md) are allowed to
create a project in a group, but might not be allowed to initially
push to the [default branch](repository/branches/index.md#default-branch).
The default branch protection level is set in the [Admin Area](../admin_area/settings/visibility_and_access_controls.md#default-branch-protection). The default branch protection level is set in the [Admin Area](../admin_area/settings/visibility_and_access_controls.md#default-branch-protection).
See the [Changelog](#changelog) section for changes over time.
## Configuring protected branches ## Configuring protected branches
To protect a branch, you need to have at least Maintainer permission level. To protect a branch, you need to have at least Maintainer permission level.
......
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