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:
Fix the Issue: Push a new commit to the source branch to fix the build failure or resolve conflicts locally.
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)
Navigate to Repository Settings > Merge queues.
Select the ... (more options) menu and choose Deactivate.
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
It looks like you're new here. Sign in or register to get started.
