You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We use Bitbucket Cloud and our strategy for PRs is to rebase the branch on the target so it becomes a fast-forward and merge with a merge commit, aligned with the Rebase, merge strategy available on Bitbucket Server. Since this is not supported by Cloud, I have to perform the rebase myself once the PR is approved, wait for the build process again and then merge. I would like for Bitbucket Cloud to perform the rebase as part of the merge process.
Here are a few issues dealing with this. It makes Bitbucket Cloud look bad. While Bitbucket server has had this feature since 2017.
It makes Bitbucket Cloud look bad.
Strong understatement there. It makes BitBucket Cloud look terrible. Users have no choice but to migrate off Server, and Cloud is missing so many features that require manual workarounds instead.
It is astounding that Cloud is missing so many basic features that Server had.
Here we are absolutely horrified about this lack of useful merge 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 as well).