The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

how to force merge after a pr in merge queue failed

蒋安立
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 7, 2026

image.png

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Tomislav Tobijas
Community Champion
June 8, 2026

Hi @蒋安立 ,

Generally, the standard workflow is to address the cause of the failure (e.g., broken tests or conflicts) and then re-add the PR to the queue:

  1. Fix the Issue: Push a new commit to the source branch to fix the build failure or resolve conflicts locally.

  2. Re-add to Queue: Once merge checks pass again, select Add to Merge Queue on the PR page

👉 Now, if you'd like to bypass it, I think you can configure merge queues in repo settings (admin only)

  1. Navigate to Repository Settings > Merge queues.

  2. Select the ... (more options) menu and choose Deactivate.

  3. Go back to your PR; the button will change from "Add to Merge Queue" to Merge.

Official announcement for merge queues for the cloud is here. 🆕

You could also troubleshoot this by trying to clear the queue and checking branch restrictions that Bitbucket uses (if any).

Cheers,
Tobi

TAGS
AUG Leaders

Atlassian Community Events