https://confluence.atlassian.com/bitbucketserver/pull-request-merge-strategies-844499235.htmlTo configure merge strategies for a repository:
If I go to my settings page, https://bitbucket.org/{repo}/admin
I do not see a Pull Requests section. I do see a Pull Requests section under navigation, but that just lists open pull requests.
You're looking at documentation for the self-hosted version of Bitbucket (known as Bitbucket Server). At the moment, there's no option for a default merge strategy in Bitbucket Cloud (bitbucket.org).
Have a look at https://confluence.atlassian.com/bitbucket/work-with-pull-requests-223220593.html#Workwithpullrequests-Mergestrategies for the right set of documentation.
This feature is now available in Bitbucket Cloud. Read more about it here: https://bitbucket.org/blog/fast-forward-merges-bitbucket-cloud-default-like
Hi Mike,
That documentation is for Bitbucket Server, which supports the default merge strategy feature.
Bitbucket Cloud is a separate product with a slightly different featureset. A default merge strategy is not yet available, but since we just released squash-on-merge, it's something we want to add to cloud soon.
Alastair
Hi Alastair,
Any news on this topic? We always squash our branches when merging but developer dicipline is hard to obtain unless enforced so this feature would be much appreciated
Desperate for this. +1
Please implement. This is a great feature to have.
+1!
+1
Please add this feature. This is such a minor setting to allow, just do it. We shouldn't need browser extensions to get simple functionality like this.
@Alastair Wilkes is there a way to set this programmatically via the API? I only see documentation for Bitbucket Server @ https://confluence.atlassian.com/bitbucketserverkb/how-to-define-a-default-merge-strategy-per-project-894207103.html.
@Peter Majeedthanks for your question. At this time, there isn't an API to set this programmatically.
Why even release a feature if you can't do it in both places. We are hacking all over the place hitting cloud endpoints that aren't documented, but totally exist because the app uses them. Why not just document and allow users to have all the wonderful power. Right now we feel hamstrung, or hacky. Either way, this does not give me confidence in Atlassian product quality. Especially when there are solutions like Github getting more and more powerful every day! TL:DRRelease a feature with an API used by the GUI, document that API and give it to the people. Anything less is disappointing at best.
It looks like you're new here. Sign in or register to get started.
