Versions
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- See all
Checks for merging pull requests
Using pull requests in Bitbucket Server
On this page
Related content
- Using repository hooks
- Pull request merge strategies
- Automatic branch merging
- Merge a pull request
- How to bulk change, enable, or disable the "auto-merge" settings for projects in Bitbucket Data Center
- How to bulk change, enable, or disable the "auto-merge" settings for projects in Bitbucket Data Center
- Review and discuss a pull request
- Using forks in Bitbucket Server
- Using pull requests in Bitbucket Server
- How to define a default merge strategy per Project
To help customize your workflow, you can set checks to control when a pull request can be merged. Pull requests cannot be merged if the required checks have not been met. These checks are set separately on each repository in a Bitbucket Server project.
You'll need either project admin, admin or sys-admin permissions to set merge checks for pull requests.
To set checks for merging pull requests, go to a repository in a project and choose Settings > Pull requests. Bitbucket Server includes the merge checks described below, or you can write your own merge request check plugin.
Requires a minimum number of approvers
Stops a pull request from being merged until it is approved by at least the selected number of participants.
Requires all reviewers to approve the pull request
Stops a pull request from being merged until all reviewers approve a pull request.
Requires all tasks to be resolved
Stops a pull request from being merged if any pull request tasks are still unresolved. Read more about pull request tasks.
Requires a minimum number of successful builds
Stops pull requests from being merged if they have any unsuccessful builds. For a pull request, this checks builds that run against the latest commit on the source branch.
You must also specify a minimum number of builds - the pull request will not be able to be merged until at least this many builds have completed. Ideally, you should set this to the number of different builds that are configured to run against the branches in your repository.
See the page Bamboo integration for more information about integrating Bitbucket Server with your build server.
Related content
- Using repository hooks
- Pull request merge strategies
- Automatic branch merging
- Merge a pull request
- How to bulk change, enable, or disable the "auto-merge" settings for projects in Bitbucket Data Center
- How to bulk change, enable, or disable the "auto-merge" settings for projects in Bitbucket Data Center
- Review and discuss a pull request
- Using forks in Bitbucket Server
- Using pull requests in Bitbucket Server
- How to define a default merge strategy per Project