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
Does Bitbucket Cloud only support 2 out of 5 supported strategies in Bitbucket Server 4.9 or am I missing something?
Thank you beforehand,
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.
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 !
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.
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?
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...