From 05fae7438ab6fbf7b21fe18e3baf2ac615bc68ee Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Tue, 19 May 2026 18:53:11 +0000 Subject: [PATCH 1/2] docs: add changelog entry for merge queue enqueue by label --- ...026-05-19-merge-queue-enqueue-by-label.mdx | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 changelog/2026-05-19-merge-queue-enqueue-by-label.mdx diff --git a/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx b/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx new file mode 100644 index 00000000..8464f809 --- /dev/null +++ b/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx @@ -0,0 +1,20 @@ +--- +title: "Merge Queue: Enqueue Pull Requests by Label" +description: "Apply a configured GitHub label to a PR to send it straight to the merge queue." +date: 2026-05-19 +category: Merge Queue +--- + +## New features + +### Merge Queue: Enqueue pull requests by label + +**You can now send a PR to the merge queue by applying a configured GitHub label**, alongside the existing `/trunk merge` comment, web app, and CLI options. + +Configure a single label per repository (for example, `merge-queue` or `ready-to-merge`) under **Settings → Repositories → Merge Queue → Enqueue by label**. Once set, applying that label to any eligible open PR enqueues it automatically, and Trunk removes the label as soon as the queue picks the PR up. + +This makes it easy to plug Trunk Merge Queue into existing label-based GitHub workflows and automations — bots, GitHub Actions, and review tools that already manage labels can now drive the merge queue without learning a new command surface. + +Note: removing the label does **not** cancel a PR that has already been picked up. Use `/trunk cancel`, the web app, or the CLI to cancel an in-flight PR. + +[Read the docs](https://docs.trunk.io/merge-queue/using-the-queue/reference#enqueueing-by-label) to learn more. From 75c6c34411ccf9e1135054e7020718ee56d55108 Mon Sep 17 00:00:00 2001 From: Sam Gutentag <1404219+samgutentag@users.noreply.github.com> Date: Tue, 26 May 2026 14:15:33 -0700 Subject: [PATCH 2/2] docs(changelog): restructure to canonical shape + wire into all 4 sites MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Restructure body to canonical changelog shape: drop h2/h3 headings, keep bold opener + paragraphs + Note callout for the cancel-caveat. Add required `type: new-feature` frontmatter. Wire the entry into the three sites the initial draft missed: - docs.json nav (under Changelog tab → 2026 group, newest first) - changelog/index.mdx (master index with tag-filter UI) - merge-queue/changelog.mdx (product-page index; adds new May 2026 section above April) Co-Authored-By: Claude Opus 4.7 (1M context) --- changelog/2026-05-19-merge-queue-enqueue-by-label.mdx | 9 ++++----- changelog/index.mdx | 6 ++++++ docs.json | 1 + merge-queue/changelog.mdx | 6 ++++++ 4 files changed, 17 insertions(+), 5 deletions(-) diff --git a/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx b/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx index 8464f809..4577f4a1 100644 --- a/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx +++ b/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx @@ -3,18 +3,17 @@ title: "Merge Queue: Enqueue Pull Requests by Label" description: "Apply a configured GitHub label to a PR to send it straight to the merge queue." date: 2026-05-19 category: Merge Queue +type: new-feature --- -## New features - -### Merge Queue: Enqueue pull requests by label - **You can now send a PR to the merge queue by applying a configured GitHub label**, alongside the existing `/trunk merge` comment, web app, and CLI options. Configure a single label per repository (for example, `merge-queue` or `ready-to-merge`) under **Settings → Repositories → Merge Queue → Enqueue by label**. Once set, applying that label to any eligible open PR enqueues it automatically, and Trunk removes the label as soon as the queue picks the PR up. This makes it easy to plug Trunk Merge Queue into existing label-based GitHub workflows and automations — bots, GitHub Actions, and review tools that already manage labels can now drive the merge queue without learning a new command surface. -Note: removing the label does **not** cancel a PR that has already been picked up. Use `/trunk cancel`, the web app, or the CLI to cancel an in-flight PR. + +Removing the label does **not** cancel a PR that has already been picked up. Use `/trunk cancel`, the web app, or the CLI to cancel an in-flight PR. + [Read the docs](https://docs.trunk.io/merge-queue/using-the-queue/reference#enqueueing-by-label) to learn more. diff --git a/changelog/index.mdx b/changelog/index.mdx index 0b368a78..7c997e1e 100644 --- a/changelog/index.mdx +++ b/changelog/index.mdx @@ -15,6 +15,12 @@ rss: true Automatic bot comment hiding, a skip-batching toggle, and Celebration Mode come to the Trunk for GitHub Chrome Extension. + + **[Merge Queue: Enqueue Pull Requests by Label](/changelog/2026-05-19-merge-queue-enqueue-by-label)** + + Apply a configured GitHub label to a PR to send it straight to the merge queue. + + **[Flaky Tests: Organization-Scoped Test Labels](/changelog/2026-05-18-flaky-tests-test-labels)** diff --git a/docs.json b/docs.json index 179c148b..16f5b00e 100644 --- a/docs.json +++ b/docs.json @@ -603,6 +603,7 @@ "group": "2026", "pages": [ "changelog/2026-05-19-merge-queue-chrome-extension-updates", + "changelog/2026-05-19-merge-queue-enqueue-by-label", "changelog/2026-05-18-flaky-tests-test-labels", "changelog/2026-05-18-flaky-tests-monitor-label-actions", "changelog/2026-05-18-flaky-tests-failure-count-monitor", diff --git a/merge-queue/changelog.mdx b/merge-queue/changelog.mdx index ef47fe82..20921534 100644 --- a/merge-queue/changelog.mdx +++ b/merge-queue/changelog.mdx @@ -15,6 +15,12 @@ rss: true Automatic bot comment hiding, a skip-batching toggle, and Celebration Mode come to the Trunk for GitHub Chrome Extension. + + **[Merge Queue: Enqueue Pull Requests by Label](/changelog/2026-05-19-merge-queue-enqueue-by-label)** + + Apply a configured GitHub label to a PR to send it straight to the merge queue. + + ### April 2026