Skip to content

docs(merge-queue): browser extension adds High priority submissions #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
samgutentag wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −1
Open

docs(merge-queue): browser extension adds High priority submissions #232

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bd412eb
docs(merge-queue): browser extension adds High priority submissions
claude Jun 10, 2026
a442c87
docs(merge-queue): drop changelog entry, keep as doc-only update
samgutentag Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion merge-queue/browser-extensions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ On any pull request in a queue-enabled repository, the extension adds a **Merge

1. Open the pull request on GitHub.
2. In the Trunk panel, click **Add to Merge Queue**.
3. Optionally choose a [priority](./optimizations/priority-merging) before submitting.
3. Optionally choose a [priority](./optimizations/priority-merging) before submitting. The dropdown includes **Normal** (default), **Low**, **High**, and **Urgent**. Urgent forces the PR to the front of the queue and restarts any in-progress testing; use it only for production incidents.
4. If batching is enabled for the repository, you can toggle **Skip batching** to enqueue this PR without grouping it into a batch — useful for hotfixes or PRs that need to merge without waiting for a batch window.

Submission goes through the same backend as the `/trunk merge` comment and the Trunk web app, so behavior is identical. See [Submit and cancel pull requests](./using-the-queue/reference) for the full lifecycle.
Expand Down