Merge Approve Document For Free

If you want to make sure every merge request is approved by one or more people, you can enforce this workflow by using merge request approvals. Merge request approvals allow you to set the number of necessary approvals and predefine a list of approvers that will need to approve every merge request in a project.

The following users can approve merge requests if they have Developer or higher permissions: Users added as approvers at the project or merge request level. Users who are Code owners of the files changed in the merge request.

Above the changed code, click Review changes. Type a comment summarizing your feedback on the proposed changes. Select Approve to approve merging the changes proposed in the pull request. Click Submit review.

Select the one you want to approve to bring up the detailed pull request page. You can approve the request by merging it into the main branch if everything looks good. Hit "Merge pull request" to begin the merge. Add a name and description, and hit "Confirm merge" to finalize the changes.

The following users can approve merge requests if they have Developer or higher permissions: Users added as approvers at the project or merge request level. Users who are Code owners of the files changed in the merge request.

NOTE: Note: The merge request author is not allowed to approve their own merge request if Prevent author approval is enabled in the project settings. Once the approval rules have been met, the merge request can be merged if there is nothing else blocking it.

In GitLab 13.10 and earlier, code owners who commit to a merge request can approve it, even if the merge request affects files they own. In GitLab 13.11 and later, code owners who commit to a merge request cannot approve it, when the merge request affects files they own.