Merge checks
By configuring merge checks, you ensure that only the pull requests that meet the specified conditions can be merged into the target branch.
Access to this feature is limited to users who already have access to CI Manager.
Default configuration
Merge check configuration is defined on the project level and, by default, inherited by each repository. You can customize this configuration separately for each repository in your project.
Note that the merge check configuration applies to all the branches within a repository.
You can configure the following merge checks:
Merge check | Description | Default configuration |
---|---|---|
All reviewers approve | Blocks the merge until all the reviewers approve the pull request. | Disabled |
Minimum approvals | Blocks the merge until the pull request receives at least the specified number of approvals. | Disabled |
Minimum successful builds | Blocks the merge until there is at least the specified number of successful builds. | Disabled |
No needs work status | Blocks the merge if any reviewer marked the pull request as needs work . | Disabled |
No incomplete tasks | Blocks the merge if there are any incomplete tasks. | Disabled |
Edit configuration
To edit merge check configuration for a repository:
-
Select a star system.
-
From
Apps, select Repository Settings or select it from your pinned apps.
-
Go to the Merge checks tab.
-
Select a repository.
-
Select a new value from the drop-down list: Enabled, Disabled, or Inherited.
For Minimum approvals and Minimum successful builds, the default value is 1. To change this value, use
Edit merge check.
You can also configure merge checks with the Repository Settings API.