We've added support for the following additional merge strategies:

• Rebase + fast forward (BCLOUD-16610)
• Rebase + merge (BCLOUD-17881, BCLOUD-19186)
• Squash, fast forward only (BCLOUD-16338)

It's also now possible to sync a feature branch via rebase (BCLOUD-6202).

https://bitbucket.org/blog/branch-sync-merge-rebase

We're working on adding support for several additional merge strategies, including:

• Rebase + fast forward (BCLOUD-16610)
• Rebase + merge (BCLOUD-17881, BCLOUD-19186)
• Squash, fast forward only (BCLOUD-16338)

Here we are absolutely horrified about the lack of useful merging and synching strategies.

We were always picky about having a clean commit history and it is impossible to enforce with the cloud version.

The good point is that this gives us additional arguments for the management to finally move away from bitbucket (and hopefully from the rest of atlassian products as well).

Excruciatingly disappointing that Bitbucket has failed to deliver such basic functionality for over 5 years now.

This is a major productivity loss requiring all PRs to need to go through a physical machine to be massaged prior to merging.

Possible duplicate of BCLOUD-16610, please feel free to vote on both issues to get basic functionality on the roadmap.

+1

+1