Versions
- 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
Using pull requests in Bitbucket Server
Using Bitbucket Server
- Creating projects
- Creating repositories
- Clone a repository
- Controlling access to code
- Workflow strategies in Bitbucket Server
- Using pull requests in Bitbucket Server
- Search for code in Bitbucket Server
- Notifications
- Markdown syntax guide
- Requesting add-ons
- Integrating Bitbucket Server with Atlassian applications
- Set the default time zone in Bitbucket Server
On this page
In this section
Related content
- No related content found
Pull requests in Bitbucket Server provide a quick and easy way for software teams to collaborate on code. A pull request is a dedicated forum for discussing a proposed feature. If there are problems with the changes, teammates can post feedback in the pull request and even tweak the feature by pushing follow-up commits. All of this activity is tracked directly inside of the pull request.
A pull request requires differences between two distinct branches. When you create a pull request you'll specify the branch to merge changes into.
Create a branch
Pull requests can be used with the Feature Branch Workflow, the Gitflow Workflow, or the Forking Workflow. You can create branches from the Bitbucket UI, from the command line using Git, or from within a connected JIRA Software instance.
Read about how to create a branch.
Create a pull request
In their simplest form, pull requests allow a developer to notify team members that they've completed a feature. Once their feature branch is ready, the developer files a pull request via their Bitbucket account. This lets everybody involved know that they need to review the code and merge it into the master branch.
Read about how to create a pull request.
Review and discuss a pull request
As a reviewer of a pull request, your colleagues are counting on you to review changes to the code then provide feedback. Use reviewer status indicators to let a pull request author know you approve the changes or that changes need more work before you can approve.
To review a pull request, select either 
Approve or 
Needs work within the header of a pull request. Click the button again or click a different one to change your status.
Read about how to review and discuss a pull request.
Merge a pull request
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.
In this section
Related content
- No related content found