Introducing merge queues for Bitbucket Cloud [open beta]

[#1]

Hi Bitbucket Community!

We're excited to announce merge queues for Bitbucket! Here's all about it from engineering manager Rajkumar Singh:

High‑traffic repos and large monorepos often suffer from “green” pull requests that still break main, endless rebases, and developers babysitting merges instead of shipping features.

Bitbucket merge queues, now in open beta for Standard and Premium Bitbucket Cloud customers, automatically sequence and validate PRs so only changes that pass checks against the latest target branch are merged. This keeps your target branch healthy while helping teams ship faster with fewer broken builds and rollbacks.

Read the full announcement and setup guide here: Introducing merge queues for Bitbucket Cloud (open beta)

Getting started

The workspace must be on a Standard or Premium plan with Pipelines enabled.

1. Open the Merge queues tab in your Repository settings → Workflow section.

2. Configure a merge queue for a specific target branch along with a new merge queue pipeline configuration in bitbucket-pipelines.yml

   1. All your pull requests targeting the specific target branch will now go through merge queue.

Want to learn more about Merge Queues and how to configure them? Go through our documentation.

Share your feedback

Your feedback is key to shaping what comes next, leave a comment below or use the in-product feedback button in Bitbucket.

[Ren]

Hi @Dan Hom

Is there API support for this yet? Checked the docs but couldn't find anything mentioning it.

Thanks!

[Rajkumar Singh]

Hi @Ren, thanks for raising this and for checking the docs!

We haven't yet exposed the merge queue specific API but there are some fields in the existing PR apis which can help you identify the status of the PR.

But to make sure we point you at the right thing (or capture a gap properly), could you share a bit more detail on which APIs you’re looking for and how you’re hoping to use them?

If you’re open to it, we’d also love to go a bit deeper on your workflow in a short call so we can understand your requirements and feed them back into the roadmap. You can grab a slot here:
Bitbucket Pipelines: Product Discussion

[Elias Thompson]

We've been exploring using merge queues on our team but we've noticed that the temporary branch that it create doesn't respect our squashed commit message, and the commit merged into our main branch doesn't follow our commitlint standards as a result. Any plans to change the commit in the temporary branch to passthrough our own commit message that we chose on PR merge?

[Thibaud Normand]

Hi!

Is there a way to specify the merge message instead of appending extra (unwanted) data to the initial commit message?

The merge queue message becomes: "Merged in *BRANCH* (pull request #*NNN*) *COMMIT MESSAGE* Approved-by: *APPROVER*"

I would like it to simply be *COMMIT MESSAGE* instead.

[Sarthak Goel]

Hi @Elias Thompson @Thibaud Normand Thanks for reporting this and for explaining what you’re trying to achieve.

We have created a bug report for the same and it could be tracked here https://jira.atlassian.com/browse/BCLOUD-24092 

Please feel free to suggest any enhancements that you'd like as well.  If you’re open to it, we’d also love to go a bit deeper on your workflow in a short call so we can understand your requirements and feed them back into the roadmap. You can grab a slot here: Bitbucket Pipelines: Product Discussion 

[Elias Thompson]

@Sarthak Goel Thanks for tracking the issue! I've booked a time slot for a colleague and I to call about merge queues and pipelines this Monday.