If someone has made changes to the original repository since you forked it, you will see that your forked repository is one or more commits behind the
original. If that is the case, to update your repository, click Sync now and then Sync on the popup that appears.
If you want to see the differences between your current repository and the original repository, click the Diff tab to compare changes. If there are multiple
commits, you see their cumulative changes by file in this section. Click the Side-by-side diff button to see changes displayed side-by-side. Or press the
View file button to view the full file in Bitbucket.
FORK A PROJECT IN BITBUCKET
MERGE PULL REQUEST
▸ (Optional) Update the Commit message with more details.
▸ (For Git repositories only) Select a Merge strategy from the two options:
▸ Merge commit—Keeps all commits from your source branch and makes them part of the destination branch. This option is the same
as entering git merge --no-ff in the command line.
▸ Squash—Combines your commits when you merge the source branch into the destination branch. This option is the same as
entering git merge --squash in the command line.
▸ (Optional) If you're merging two branches in the same repository, you can select the Close source branch checkbox to remove the
branch from the list of repository branches.
▸ Click the Merge button.
Decline a pull request
Declining a pull request cannot be undone. Once you decline a pull request you will have to open a new
pull request request to continue a review.
Declining a pull request has no effect on the branches (source or destination) so the changes in the
source branch are still in that source branch.
DECLINE A PULL REQUEST