Bypass the merge queue entirely for true emergencies. Use with caution as this can invalidate in-progress queue tests.
Emergency merges bypass the queue entirely and push directly to your main branch. This is the most disruptive action you can take and should be reserved for true emergencies only.
Warning: Emergency merges bypass all safety checks. Use sparingly.
If you need to completely bypass the merge queue, you can merge the PR directly through GitHub as you normally would. The merge queue will restart everything currently testing to account for the new head of the merge branch. However, this means your emergency PR won’t be validated by the merge queue’s predictive testing.
Use PR Prioritization to fast-track your PR through the queue while still validating it:
/trunk merge --priority=urgent
The urgent priority is the only level that will interrupt currently testing PRs. Your PR will immediately begin testing, and other PRs will restart after yours completes.
If the blocker is branch protection (not the queue) — for example, a broken required status check — admins can use Direct to queue instead. Direct to queue still goes through the queue and still tests the PR; only the branch protection gate is bypassed at merge time.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.
