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
fc87880c
Commit
fc87880c
authored
Jun 07, 2019
by
Matt Penna
Committed by
MattPennaThe3rd
Jun 07, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added links to pertinent GitLab docs
Clarified who can push to a protected branch
parent
be1d1c70
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
2 deletions
+3
-2
doc/security/information_exclusivity.md
doc/security/information_exclusivity.md
+3
-2
No files found.
doc/security/information_exclusivity.md
View file @
fc87880c
...
...
@@ -18,8 +18,9 @@ This is an inherent feature of a DVCS. All git management systems have this
limitation.
You can take steps to prevent unintentional sharing and information
destruction. This is the reason why only certain people are allowed to invite
others and why no user can force push a protected branch.
destruction. This limitation is the reason why only certain people are allowed
to
[
add users to a project
](
../user/project/members/
)
and why only a GitLab
admin can
[
force push a protected branch
](
../project/protected_branches.html
)
.
<!-- ## Troubleshooting
...
...
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