diff options
| author | Matt Penna <mpenna@gitlab.com> | 2019-09-11 01:52:38 +0000 |
|---|---|---|
| committer | Matt Penna <mpenna@gitlab.com> | 2019-09-11 01:52:38 +0000 |
| commit | a8da7b00706e3ff3678f5a34abdf6b894f29eed6 (patch) | |
| tree | 99321dfc07add5a3b892768981023cfbe82fa87c | |
| parent | 28c23be6f72959fe4b1051bdb0d5ff421a316ade (diff) | |
| download | gitlab-ce-docs-permissions-clarify-mpenna20190906.tar.gz | |
Apply suggestion to doc/user/permissions.mddocs-permissions-clarify-mpenna20190906
| -rw-r--r-- | doc/user/permissions.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/user/permissions.md b/doc/user/permissions.md index 62ce498b33c..13a823a71ee 100644 --- a/doc/user/permissions.md +++ b/doc/user/permissions.md @@ -151,9 +151,7 @@ which visibility level you select on project settings. ### Protected branches -In cases where you want to prevent Developers or other project members from changing commit history -or from pushing code without review, you can use a [protected branch](project/protected_branches.md). - +Additional restrictions can be applied on a per-branch basis with [protected branches](project/protected_branches.md). Additionally, you can customize permissions to allow or prevent project Maintainers and Developers from pushing to a protected branch. Read through the documentation on [Allowed to Merge and Allowed to Push settings](project/protected_branches.md#using-the-allowed-to-merge-and-allowed-to-push-settings) |