summaryrefslogtreecommitdiff
path: root/doc/workflow
diff options
context:
space:
mode:
authorPatricio Cano <patricio@gitlab.com>2015-05-05 16:14:54 +0000
committerPatricio Cano <patricio@gitlab.com>2015-05-05 16:14:54 +0000
commit69f3b400316d065a05830dabfb55d78ae8cecef5 (patch)
tree0232585c5de41713a2e2a82b11a6016f28c5f825 /doc/workflow
parent1132084d3fcbb5623546730a6269b2a5d1c2ada3 (diff)
downloadgitlab-ce-69f3b400316d065a05830dabfb55d78ae8cecef5.tar.gz
Fixed broken permissions link.
Diffstat (limited to 'doc/workflow')
-rw-r--r--doc/workflow/protected_branches.md6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/workflow/protected_branches.md b/doc/workflow/protected_branches.md
index 805f7f8d35c..0adf9f8e3e8 100644
--- a/doc/workflow/protected_branches.md
+++ b/doc/workflow/protected_branches.md
@@ -12,7 +12,7 @@ A protected branch does three simple things:
You can make any branch a protected branch. GitLab makes the master branch a protected branch by default.
-To protect a branch, user needs to have at least a Master permission level, see [permissions document](permissions/permissions.md).
+To protect a branch, user needs to have at least a Master permission level, see [permissions document](doc/permissions/permissions.md).
![protected branches page](protected_branches/protected_branches1.png)
@@ -28,6 +28,4 @@ For those workflows, you can allow everyone with write access to push to a prote
On already protected branches you can also allow developers to push to the repository by selecting the `Developers can push` check box.
-![Developers can push](protected_branches/protected_branches2.png)
-
-
+![Developers can push](protected_branches/protected_branches2.png) \ No newline at end of file