Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
34160b5f
Commit
34160b5f
authored
4 years ago
by
Sean Carroll
Committed by
Amy Qualls
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Allow reporters to approve MRs documentation
Part of
#225485
See merge request
!41743
parent
bb892681
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/user/project/merge_requests/img/update_approval_rule_v13_4.png
+0
-0
0 additions, 0 deletions
...project/merge_requests/img/update_approval_rule_v13_4.png
doc/user/project/merge_requests/merge_request_approvals.md
+23
-0
23 additions, 0 deletions
doc/user/project/merge_requests/merge_request_approvals.md
with
23 additions
and
0 deletions
doc/user/project/merge_requests/img/update_approval_rule_v13_4.png
0 → 100644
+
0
−
0
View file @
34160b5f
31.3 KiB
This diff is collapsed.
Click to expand it.
doc/user/project/merge_requests/merge_request_approvals.md
+
23
−
0
View file @
34160b5f
...
...
@@ -121,6 +121,29 @@ indistinguishably.
Alternatively, you can
**require**
[
Code Owner's approvals for Protected Branches
](
../protected_branches.md#protected-branches-approval-by-code-owners
)
.
**(PREMIUM)**
#### Merge Request approval segregation of duties
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/40491) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.4.
Managers or operators with
[
Reporter permissions
](
../permissions.md#project-members-permissions
)
to a project sometimes need to be required approvers of a merge request,
before a merge to a protected branch begins. These approvers aren't allowed
to push or merge code to any branches.
To enable this access:
1.
[
Create a new group
](
../../group/index.md#create-a-new-group
)
, and then
[
add the user to the group
](
../../group/index.md#add-users-to-a-group
)
,
ensuring you select the Reporter role for the user.
1.
[
Share the project with your group
](
../members/share_project_with_groups.md#sharing-a-project-with-a-group-of-users
)
,
based on the Reporter role.
1.
Navigate to your project's
**Settings > General**
, and in the
**Merge request approvals**
section, click
**Expand**
.
1.
[
Add the group
](
../../group/index.md#create-a-new-group
)
to the permission list
for the protected branch.

#### Adding / editing a default approval rule
To add or edit the default merge request approval rule:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment