• Auto-merge a merge request
• Cancel an auto-merge
• Pipeline success for auto-merge
  • Require a successful pipeline for merge
  • Allow merge after skipped pipelines
• Prevent merge before a specific date
• Troubleshooting
  • Merge request can’t merge despite no failed pipeline
  • Merge request can still be merged despite a failed pipeline

Auto-merge

If the content of a merge request is ready to merge, you can select Set to auto-merge. The merge request auto-merges when all required checks complete successfully, and you don’t need to remember to manually merge the merge request.

Merge checks enable you to focus on reviewing a merge request’s contents, and use project settings to determine their mergeability. When you review a merge request, if you approve of the merge request’s changes, set it to auto-merge. GitLab enforces your project settings, and until the merge request satisfies all merge checks (like required Code Owner and approval rules), it cannot merge. After satisfying all required merge checks, the merge request merges, with no action required from you.

Merge checks include a passing CI/CD pipeline, and much more:

• All required approvals must be given.
• No other merge requests block this merge request.
• No merge conflicts exist.
• A CI/CD pipeline must complete successfully, regardless of the project setting.
• All discussions are resolved.
• The merge request is not a Draft.
• All external status checks have passed.
• The merge request must be open.
• No denied policies exist.
• If your project requires merge requests to reference a Jira issue, the merge request title or description contains a Jira issue link.
• If the merge request has a Merge after date set, the current time must be after the configured date.

For a full list of checks and their API equivalents, see Merge status.

After you set auto-merge, you can’t change which issues auto-close when the merge request merges.

Auto-merge a merge request

Prerequisites:

• You must have at least the Developer role for the project.
• If your project configuration requires it, all threads in the merge request must be resolved.
• The merge request must have received all required approvals.

To do this when pushing from the command line, use the merge_request.merge_when_pipeline_succeeds push option.

To do this from the GitLab user interface:

1. On the left sidebar, select Search or go to and find your project.
2. Select Code > Merge requests.
3. Select the merge request to edit.
4. Scroll to the merge request reports section.
5. Optional. Select your desired merge options, such as Delete source branch, Squash commits, or Edit commit message.
6. Review the contents of the merge request widget. If it contains an issue closing pattern, confirm that the issue should close when this work merges:
7. Select Auto-merge.

Commenting on a merge request after you select Auto-merge, but before the pipeline completes, blocks the merge until you resolve all existing threads.

Cancel an auto-merge

You can cancel auto-merge on a merge request.

Prerequisites:

• You must either be the author of the merge request, or a project member with at least the Developer role.
• The merge request’s pipeline must still be in progress.

To do this:

1. On the left sidebar, select Search or go to and find your project.
2. Select Code > Merge requests.
3. Select the merge request to edit.
4. Scroll to the merge request reports section.
5. Select Cancel auto-merge.

Pipeline success for auto-merge

If the pipeline succeeds, the merge request merges. If the pipeline fails, the author can either retry any failed jobs, or push new commits to fix the failure:

• If a retried job succeeds on the second try, the merge request merges.
• If you add new commits to the merge request, GitLab cancels the request to ensure the new changes receive a review before merge.
• If you add new commits to the target branch of the merge request, and your project allows only fast-forward merge requests, GitLab cancels the request to prevent merge conflicts.

For stricter control on pipeline status, you can also require a successful pipeline before merge.

Require a successful pipeline for merge

You can configure your project to require a complete and successful pipeline before merge. This configuration works for both:

• GitLab CI/CD pipelines.
• Pipelines run from an external CI integration.

As a result, disabling GitLab CI/CD pipelines does not disable this feature, but you can use pipelines from external CI providers with it.

Prerequisites:

• Ensure your project’s CI/CD configuration runs a pipeline for every merge request.
• You must have at least the Maintainer role for the project.

To enable this setting:

1. On the left sidebar, select Search or go to and find your project.
2. Select Settings > Merge requests.
3. Scroll to Merge checks, and select Pipelines must succeed. This setting also prevents merge requests from merging if there is no pipeline, which can conflict with some rules.
4. Select Save.

If multiple pipeline types run for the same merge request, merge request pipelines take precedence over other pipeline types. For example, an older but successful merge request pipeline allows a merge request to merge, despite a newer but failed branch pipeline.

Allow merge after skipped pipelines

When you set Pipelines must succeed for a project, skipped pipelines prevent merge requests from merging.

Prerequisites:

• You must have at least the Maintainer role for the project.

To change this behavior:

1. On the left sidebar, select Search or go to and find your project.
2. Select Settings > Merge requests.
3. Under Merge checks:
   • Select Pipelines must succeed.
   • Select Skipped pipelines are considered successful.
4. Select Save.

Prevent merge before a specific date

If your merge request should not merge before a specific date and time, set a Merge after date. This value sets when the merge (or merge train) can start. The exact time of merge can vary, however, depending on the satisfaction of other merge checks or the length of your merge train.

Prerequisites:

• You must have at least the Developer role for the project.

To do this:

1. On the left sidebar, select Search or go to and find your project.
2. Select Code > Merge requests.
3. Select the merge request to edit.
4. Select Edit.
5. Find the Merge after input and select a date and time.
6. Select Save changes.

Troubleshooting

Merge request can’t merge despite no failed pipeline

In some cases, you can require a successful pipeline for merge, but be unable to merge a merge request with no failed pipelines. The setting requires the existence of a successful pipeline, not the absence of failed pipelines. A merge request with no pipelines at all is not considered to have a successful pipeline, and cannot merge.

When you enable this setting, use rules or workflow:rules to ensure pipelines run for every merge request.

Merge request can still be merged despite a failed pipeline

In some cases, you can require a successful pipeline for merge, but still merge a merge request with a failed pipeline.

Merge request pipelines have the highest priority for the Pipelines must succeed setting. If multiple pipeline types run for the same merge request, GitLab checks only the merge request pipelines for success.

Merge requests can have multiple pipelines if:

• A rules configuration that causes duplicate pipelines: one merge request pipeline and one branch pipeline. In this case, the status of the latest merge request pipeline determines if a merge request can merge, not the branch pipeline.
• Pipelines triggered by external tools that target the same branch as the merge request.

In all cases, update your CI/CD configuration to prevent multiple pipeline types for the same merge request.