summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMark Chao <mchao@gitlab.com>2018-06-06 11:41:24 +0900
committerMark Chao <mchao@gitlab.com>2018-06-06 21:01:47 +0900
commitdd42cab9da1f4d47485a1a20e7ce055a8b39dbe1 (patch)
treed48f40c6d84d1adbd59ff9135449896ee201412b /doc
parent9980869d1ea0db1a73c643ec42e21d409ead187c (diff)
downloadgitlab-ce-dd42cab9da1f4d47485a1a20e7ce055a8b39dbe1.tar.gz
Update gitlab flow doc
Diffstat (limited to 'doc')
-rw-r--r--doc/workflow/gitlab_flow.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md
index 23b67310d25..a7313082fac 100644
--- a/doc/workflow/gitlab_flow.md
+++ b/doc/workflow/gitlab_flow.md
@@ -131,7 +131,7 @@ There is room for more feedback and after the assigned person feels comfortable
If the assigned person does not feel comfortable they can close the merge request without merging.
In GitLab it is common to protect the long-lived branches (e.g. the master branch) so that normal developers [can't modify these protected branches](http://docs.gitlab.com/ce/permissions/permissions.html).
-So if you want to merge it into a protected branch you assign it to someone with master authorizations.
+So if you want to merge it into a protected branch you assign it to someone with maintainer authorizations.
## Issue tracking with GitLab flow