diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-28 06:15:46 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-28 06:15:46 +0300 |
| commit | ae4e46452b8799acd538fb96edfc60ba3214cefb (patch) | |
| tree | ae5e11b7931520642941e498fe5a681c5d85adb7 /doc/user/project/protected_branches.md | |
| parent | 35130a8688fe39829308c3c184eae87c2a170a49 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/protected_branches.md')
| -rw-r--r-- | doc/user/project/protected_branches.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/protected_branches.md b/doc/user/project/protected_branches.md index 66be849a7b9..fed0823466e 100644 --- a/doc/user/project/protected_branches.md +++ b/doc/user/project/protected_branches.md @@ -173,8 +173,8 @@ When enabled, members who are can push to this branch can also force push. ## Require Code Owner approval on a protected branch **(PREMIUM)** -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13251) in GitLab Premium 12.4. -> - [In](https://gitlab.com/gitlab-org/gitlab/-/issues/35097) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.5 and later, users and groups who can push to protected branches do not have to use a merge request to merge their feature branches. This means they can skip merge request approval rules. +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13251) in GitLab 12.4. +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/35097) in GitLab 13.5, users and groups who can push to protected branches do not have to use a merge request to merge their feature branches. This means they can skip merge request approval rules. For a protected branch, you can require at least one approval by a [Code Owner](code_owners.md). |