Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
9fa8bf03
Commit
9fa8bf03
authored
Jun 03, 2018
by
Mark Chao
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc
parent
968e4ea2
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
3 deletions
+3
-3
doc/user/group/index.md
doc/user/group/index.md
+2
-2
doc/user/project/protected_branches.md
doc/user/project/protected_branches.md
+1
-1
No files found.
doc/user/group/index.md
View file @
9fa8bf03
...
@@ -160,12 +160,12 @@ There are two different ways to add a new project to a group:
...
@@ -160,12 +160,12 @@ There are two different ways to add a new project to a group:
Group owners or administrators can set an option that will give users with the
Group owners or administrators can set an option that will give users with the
Developer role the ability to create projects under groups.
Developer role the ability to create projects under groups.
By default,
`Developers`
and
`Ma
st
ers`
are allowed to create projects under a
By default,
`Developers`
and
`Ma
intain
ers`
are allowed to create projects under a
group, but this can be changed either within the group settings for a group, or
group, but this can be changed either within the group settings for a group, or
be set globally by a GitLab administrator in the Admin area
be set globally by a GitLab administrator in the Admin area
(
**Settings > Visibility and Access Controls**
).
(
**Settings > Visibility and Access Controls**
).
The setting can set to "None", "Ma
sters", or "Developers + Mast
ers".
The setting can set to "None", "Ma
intainers", or "Developers + Maintain
ers".
## Transfer projects into groups
## Transfer projects into groups
...
...
doc/user/project/protected_branches.md
View file @
9fa8bf03
...
@@ -71,7 +71,7 @@ they are set to "Maintainers" by default.
...
@@ -71,7 +71,7 @@ they are set to "Maintainers" by default.
> This feature was [introduced][ce-5081] in [GitLab Starter][ee] 8.11.
> This feature was [introduced][ce-5081] in [GitLab Starter][ee] 8.11.
With GitLab Enterprise Edition you can restrict access to protected branches
With GitLab Enterprise Edition you can restrict access to protected branches
by choosing a role (Ma
st
ers, Developers) as well as certain users. From the
by choosing a role (Ma
intain
ers, Developers) as well as certain users. From the
dropdown menu select the role and/or the users you want to have merge or push
dropdown menu select the role and/or the users you want to have merge or push
access.
access.
...
...
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