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
- 4.13
- 4.12
- 4.11
- 4.10
- 4.9
- 4.8
- 4.7
- See all
Merge a pull request
Using pull requests in Bitbucket Server
On this page
Related content
- Raising a request with Atlassian Support
- How to configure SAML SSO for Bitbucket Data Center with OKTA
- Connecting Bitbucket Server to JIRA for user management
- Support policies
- Bitbucket Data Center and Server Knowledge Base
- Requesting add-ons
- What is the Bitbucket Server ID?
- Linking Bitbucket Server with JIRA
- Updating your Bitbucket Server license details
- Automated setup for Bitbucket Server
Once you are ready to merge a pull request, and when the reviewers have approved it, click Merge at the top right of the pull request view. You can merge a pull request if you have write (or admin) permission on the project.
Bitbucket Server does not enforce particular review workflows, so anyone with write permission on the repository can merge a pull request, including the person who opened it. This flexibility allows different teams to have different approaches to using Bitbucket Server. If your team requires stricter control, consider using branch permissions to restrict who can merge a pull request to particular users or groups. You might also want to consider using a plugin to enforce a particular workflow, for example to ensure that only approvals from members of your review team allow merging. See Checks for merging pull requests.
In the 'Merge Pull Request' dialog, you can add extra information about the pull request:
The text you add appears between the subject line and the log lines that Bitbucket Server and Git generate.
Check Delete source branch after merging if you no longer need that branch in the repository. Bitbucket Server checks on a few things before allowing the deletion – the branch being merged will not be deleted if:
- The branch is the default repository branch.
- The user does not have permission to delete the branch.
- The branch is subject to an open pull request.
Once accepted, the pull request is marked as merged on the Pull requests tab.
If Bitbucket Server detects a conflict that prevents the merge, notifications are displayed on the Overview and Diff tabs of the pull request. Click More information to see instructions for how to resolve the conflict in your local repository.
Related content
- Raising a request with Atlassian Support
- How to configure SAML SSO for Bitbucket Data Center with OKTA
- Connecting Bitbucket Server to JIRA for user management
- Support policies
- Bitbucket Data Center and Server Knowledge Base
- Requesting add-ons
- What is the Bitbucket Server ID?
- Linking Bitbucket Server with JIRA
- Updating your Bitbucket Server license details
- Automated setup for Bitbucket Server