From 7d972f9af9a393bf8dddab2d782bdee4715fbfc4 Mon Sep 17 00:00:00 2001 From: Sam Gutentag <1404219+samgutentag@users.noreply.github.com> Date: Thu, 7 May 2026 15:43:26 -0700 Subject: [PATCH] docs(chrome-extension): salvage useful bits from #588 Pulls forward the small bits worth keeping from Eli's original Chrome Extension docs PR, since the page itself has evolved well past that draft via several subsequent merged PRs. - Add a frontmatter description so GitBook renders proper metadata - Add an inline pointer to the Submit and cancel pull requests reference page after the Submit steps, so readers can drill into the full lifecycle from this entry point - Replace the FAQ link to a hard-coded GitHub commit URL with a relative path to getting-started, matching the rest of the docs Closes the conflict-stale #588 in favor of these targeted edits on top of the current main. Co-Authored-By: Claude Opus 4.7 (1M context) --- merge-queue/chrome-extension.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/merge-queue/chrome-extension.md b/merge-queue/chrome-extension.md index 64f2b75f..db74e8a1 100644 --- a/merge-queue/chrome-extension.md +++ b/merge-queue/chrome-extension.md @@ -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.\ @@ -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. + ### Remove a pull request from the queue If a PR is already in the queue, the panel shows a **Cancel** action. @@ -66,7 +72,7 @@ The extension does **not** ask you for credentials, API tokens, or a separate pa Do I need to setup anything besides the extension? -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.