Skip to content

G
gitlab-ce
Commit e466aeb8 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis
Browse files
Options

Conform to doc styleguide on new features

parent 16f48489
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
doc/user/project/protected_branches.md
View file @ e466aeb8
...@@ -43,7 +43,7 @@ that the `master` branch is protected by default. ...@@ -43,7 +43,7 @@ that the `master` branch is protected by default.
## Using the Allowed to merge and Allowed to push settings ## Using the Allowed to merge and Allowed to push settings
> This feature was [introduced][ce-5081] in GitLab 8.11. > [Introduced][ce-5081] in GitLab 8.11.
Since GitLab 8.11, we added another layer of branch protection which provides Since GitLab 8.11, we added another layer of branch protection which provides
more granular management of protected branches. The "Developers can push" more granular management of protected branches. The "Developers can push"
...@@ -73,7 +73,7 @@ they are set to "Masters" by default. ...@@ -73,7 +73,7 @@ they are set to "Masters" by default.
## Wildcard protected branches ## Wildcard protected branches
> This feature was [introduced][ce-4665] in GitLab 8.10. > [Introduced][ce-4665] in GitLab 8.10.
You can specify a wildcard protected branch, which will protect all branches You can specify a wildcard protected branch, which will protect all branches
matching the wildcard. For example: matching the wildcard. For example:
......
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
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7