Skip to content

[ready to merge] docs(chrome-extension): salvage useful bits from #588 #643

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

Merged
trunk-staging-io merged 1 commit into from
May 7, 2026
+7 −1
Merged

[ready to merge] docs(chrome-extension): salvage useful bits from #588 #643

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 7 additions & 1 deletion merge-queue/chrome-extension.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
---
description: Submit, cancel, and track Trunk Merge Queue pull requests directly from GitHub with the Trunk Chrome Extension.
---

# Chrome Extension

The Trunk Chrome Extension overlays merge queue controls and status onto your normal GitHub experience, so you can submit a PR to the queue, cancel it, and watch its testing progress without leaving the pull request page.\
Expand Down Expand Up @@ -29,6 +33,8 @@ On any pull request in a queue-enabled repository, the extension adds a **Merge
3. Optionally choose a [priority](optimizations/priority-merging.md) before submitting.
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.md) for the full lifecycle.
Copy link
Copy Markdown
Contributor

@claude claude Bot May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit, non-blocking: the first half of this sentence ("Submission goes through the same backend as the /trunk merge comment and the Trunk web app, so behavior is identical") overlaps closely with the FAQ entry below ("How does the extension differ from the /trunk merge comment?"), which says "Both go through the same Trunk Merge Queue backend." If you want to deduplicate, you could trim this to just the pointer — e.g., "See Submit and cancel pull requests for the full lifecycle." — and let the FAQ keep the equivalence claim. Up to you; either way is fine.


### Remove a pull request from the queue

If a PR is already in the queue, the panel shows a **Cancel** action.
Expand Down Expand Up @@ -66,7 +72,7 @@ The extension does **not** ask you for credentials, API tokens, or a separate pa

<summary><strong>Do I need to setup anything besides the extension?</strong></summary>

Yes - the extension is an add-on on top of Trunk Merge Queue. Your repository must have the [Trunk GitHub App installed and a queue configured](https://github.com/trunk-io/docs/blob/1a152d61c3091e1007ee9fe70406084fbe06de80/merge-queue/getting-started) before the overlay does anything useful.
Yes - the extension is an add-on on top of Trunk Merge Queue. Your repository must have the [Trunk GitHub App installed and a queue configured](getting-started/) before the overlay does anything useful.

</details>

Expand Down
Loading