BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
e466aeb8
Commit
e466aeb8
authored
Aug 22, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Conform to doc styleguide on new features
parent
16f48489
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
protected_branches.md
doc/user/project/protected_branches.md
+2
-2
No files found.
doc/user/project/protected_branches.md
View file @
e466aeb8
...
...
@@ -43,7 +43,7 @@ that the `master` branch is protected by default.
## Using the Allowed to merge and Allowed to push settings
>
This feature was [i
ntroduced][ce-5081] in GitLab 8.11.
>
[I
ntroduced][ce-5081] in GitLab 8.11.
Since GitLab 8.11, we added another layer of branch protection which provides
more granular management of protected branches. The "Developers can push"
...
...
@@ -73,7 +73,7 @@ they are set to "Masters" by default.
## Wildcard protected branches
>
This feature was [i
ntroduced][ce-4665] in GitLab 8.10.
>
[I
ntroduced][ce-4665] in GitLab 8.10.
You can specify a wildcard protected branch, which will protect all branches
matching the wildcard. For example:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment