Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

See all 5 Pull request merge strategies in Bitbucket Cloud

According to, there are 5 different merge strategy options available for merging pull requests, however I can only see 2 of them from my Bitbucket Cloud account:
-Merge commit --no-ff
-Squash --squash

Does Bitbucket Cloud only support 2 out of 5 supported strategies in Bitbucket Server 4.9 or am I missing something?

Thank you beforehand,

6 answers

Not having a `rebase + merge --ff-only` option is a deal breaker for me. Could this please be prioritized?

It's been a year, any updates on this?

Like # people like this

Hi guys!


Just a friendly reminder that this option would be quite useful and that actually has been sitting here for quite a while, can we expect to have this option implemented sometime in the (hopefully, near) future?


We are missing the `rebase` option as well.



Ya, we're considering moving away from BitBucket because of the lack of rebase.

We were looking at moving to Jira for Project Management because of its close integration with Bitbucket, but we're holding off for now until we figure out what we do with this.

Same here, please integrate: rebase + merge --ff-only, otherwise Azure DevOps will be our new friend


Any update about it ? 

It is really disturbing with the branch permission's check "Reset approvals when the source branch is modified" because our teams need to manually rebase their jobs before merging and reapprove the pull requests. 

You thinks that's normal ? Me NO !

0 votes
Tim Pettersen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 05, 2017

Hi Victor,

You're correct. Sorry for the confusion. There are variances in the feature set offered by the Cloud and Server versions of Bitbucket, and in this case Server is slightly ahead of Cloud in terms of functionality. For now, Bitbucket Cloud currently supports only a subset of the merge strategies available in Bitbucket Server. 



Any update on this suggestions ?

There is a 4 years old ticket about this issues !!!

Like # people like this

Any updates on this, I really want the rebase + merge --no-ff option available.

Any updates on when this will be available on BitBucket Cloud? We also use the "rebase + merge --no-ff" option to merge feature branches.

Not having a rebase + merge --ff-only option is a deal breaker for me. Could this please be prioritized?

Is it still not a thing on the cloud? This is a very key feature for big project

Like Michael Fasani likes this
Deleted user Mar 22, 2019

This feature would save me a couple hours each week of checkout out branch, rebasing, and then push --force before finally merging.

Like # people like this

hi @[deleted] could you elaborate on how you do rebase & merge? I understand you check out the PR branch, rebase master onto it, check out master, rebase the PR branch onto master and then push --force?

@Rodolfo Ortiz with the PR branch being checked out:

git fetch --all
git rebase origin/master
git push -f

You only rebase the feature branch on top of master, it doesn't make sense to rebase master on your feature branch.

Got it @mafa . And then, in order to merge, you would only need to do this to achieve a rebase&merge right?

git checkout master
git merge --no-ff PR_branch_being_checked_out
git push

Like Ray Depew likes this

Yes exactly

> "For now,"

It's _now_ 2021. How long is this "for now" period supposed to last? Asking for a friend.

Like # people like this

Almost 4 months into 2022 and its still missing. but I have fancy new UI that noone asked for...

My team refuses to accept merge commits which prevents us from using pull requests.

Is there some way I can mark the PR merged without actually merging it?

Also, is somebody from Atlassian actually monitoring community threads?

Is it possible to build a plugin to support it?

Like Daniel Marra likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events