According to https://confluence.atlassian.com/bitbucketserver/pull-request-merge-strategies-844499235.html, 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 --squashDoes Bitbucket Cloud only support 2 out of 5 supported strategies in Bitbucket Server 4.9 or am I missing something?Thank you beforehand,Victor
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.
cheers,
Tim
Any update on this suggestions ?
There is a 4 years old ticket about this issues !!!
https://bitbucket.org/site/master/issues/6106/provide-the-option-to-use-git-merge-ff
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?
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.
Thanks!
It's been a year, any updates on this?
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.
Looks like Azure DevOps supports this:
https://devblogs.microsoft.com/devops/pull-requests-with-rebase/
Same here, please integrate: rebase + merge --ff-only, otherwise Azure DevOps will be our new friend
Hi,
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 !
This is SO BASIC. You have this in Jira Server just port it already.https://confluence.atlassian.com/bitbucketserver050/pull-request-merge-strategies-913474859.html
gitlab too
It looks like you're new here. Sign in or register to get started.
