How do you set the default merge strategy?

[Mike Blandford]

https://confluence.atlassian.com/bitbucketserver/pull-request-merge-strategies-844499235.html

To configure merge strategies for a repository:

1. In repository settings, select Pull requests.
   
   
   

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.

[Alastair Wilkes · Accepted solution]

This feature is now available in Bitbucket Cloud. Read more about it here: https://bitbucket.org/blog/fast-forward-merges-bitbucket-cloud-default-like

[Peter Majeed]

@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.

[Alastair Wilkes]

@Peter Majeedthanks for your question. At this time, there isn't an API to set this programmatically.

[John Gill]

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:DR
Release a feature with an API used by the GUI, document that API and give it to the people. Anything less is disappointing at best. 

[Alastair Wilkes]

Thanks for the feedback, John. While we've recently made considerable improvements to the 2.0 APIs, we still have a ways to go -- especially when it comes to repository configuration management.

[Michel Zanini]

Hi @Alastair Wilkes ,

Is there any way I can set a default merge strategy to squash for all repositories belonging to a team on Bitbucket Cloud?

I need to define this globally for all repositories not one by one individually.

Or, do that it could be individually per repository if there was an API for it.

We need to do this for our CI/CD process.

Thanks.

[Alastair Wilkes]

Hi @Michel Zanini,

Thanks for your question. At this time, there isn't an easy way to do that; you'll need to set it one-by-one, in the UI. This is obviously suboptimal, and we need to make this easier in the future.

Thanks,

Alastair

[Neville Stokes]

Any progress on this?

[Peter Majeed]

FWIW, there is an issue tracked for this @ https://jira.atlassian.com/browse/BCLOUD-16387. Please vote for it. (There is one quasi-workaround at the moment.)

[Peter Majeed]

FWIW, we are planning on canceling our subscription with Bitbucket and moving to another provider because of the lack of customizations like this that damages the developer experience.

[jredmond · Accepted solution]

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.

[Alastair Wilkes]

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

[Carl Nordenfelt]

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 :)

[Kristin Jones]

Desperate for this. +1

[glrdadmin]

Please implement.  This is a great feature to have.

+1!

[Dan Baggott]

+1  Is there a ticket tracking this feature request? 

[Alastair Wilkes]

Yes, there is. It is:

https://bitbucket.org/site/master/issues/13895/default-merge-strategy

[Dan Baggott]

Thank you!

[John Gill]

Over a year later and no options yet? But hey Stride is out... oh wait we all use Slack. 

Please Atlassian, stop trying to expand and just make your products work... this should be a CORE feature of Bitbucket, not an idea that still isn't implemented after a year.

+1 to get this done.  

[Matt Mikitka]

+1

[Christopher Olekas]

+1

[Ryan Collier]

+1

[Yohan GREMBER]

+1

[Alastair Wilkes]

@Yohan GREMBERthis feature actually shipped a little while ago! You can read it about it here: https://bitbucket.org/blog/fast-forward-merges-bitbucket-cloud-default-like

[Vincent Grace]

+1

[Justin LaVelle]

+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.