Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
19 changes: 19 additions & 0 deletions changelog/2026-05-19-merge-queue-enqueue-by-label.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
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
---

**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.

Check warning on line 11 in changelog/2026-05-19-merge-queue-enqueue-by-label.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/2026-05-19-merge-queue-enqueue-by-label.mdx#L11

Did you really mean 'enqueues'?

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.

Check warning on line 13 in changelog/2026-05-19-merge-queue-enqueue-by-label.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/2026-05-19-merge-queue-enqueue-by-label.mdx#L13

Did you really mean 'automations'?

<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.
</Note>

[Read the docs](https://docs.trunk.io/merge-queue/using-the-queue/reference#enqueueing-by-label) to learn more.
6 changes: 6 additions & 0 deletions changelog/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@
Automatic bot comment hiding, a skip-batching toggle, and Celebration Mode come to the Trunk for GitHub Chrome Extension.
</Update>

<Update label="May 19, 2026" tags={["Merge Queue"]}>
**[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.
</Update>

<Update label="May 18, 2026" tags={["Flaky Tests"]}>
**[Flaky Tests: Failure Count Monitor](/changelog/2026-05-18-flaky-tests-failure-count-monitor)**

Expand Down Expand Up @@ -57,7 +63,7 @@
<Update label="March 27, 2026" tags={["Flaky Tests"]}>
**[Flaky Tests: Automatically Create Jira Issues from Webhooks](/changelog/2026-03-27-flaky-tests-automatically-create-jira-issues-from-webhooks)**

A new Jira connector in your webhook settings creates issues in your Jira Cloud project whenever a test's status changes to flaky and impacts more than a configurable number of PRs.

Check warning on line 66 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L66

Did you really mean 'Jira'?

Check warning on line 66 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L66

Did you really mean 'Jira'?
</Update>

<Update label="March 26, 2026" tags={["Merge Queue"]}>
Expand All @@ -69,7 +75,7 @@
<Update label="March 25, 2026" tags={["Merge Queue"]}>
**[Merge Queue: Multiple Queues Per Repo with Grouped Selector](/changelog/2026-03-25-merge-queue-multiple-queues-per-repo-with-grouped-selector)**

Previously, a repo could only have one queue. Now you can create additional queues from the merge queue creation page. The repo selector shows repos that already have queues and how many exist.

Check warning on line 78 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L78

Did you really mean 'repos'?
</Update>

<Update label="March 25, 2026" tags={["Merge Queue"]}>
Expand Down Expand Up @@ -228,7 +234,7 @@
<Update label="August 25, 2025" tags={["Flaky Tests"]}>
**[Flaky Tests: New endpoint and XCode 26 support](/changelog/2025-08-25-flaky-tests-new-endpoint-and-xcode-26-support)**

A new endpoint is available from the trunk api at /flaky-tests/list-unhealthy-tests for your CI/CD integrations.

Check warning on line 237 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L237

Did you really mean 'api'?
</Update>

<Update label="August 15, 2025" tags={["CI Autopilot"]}>
Expand Down Expand Up @@ -268,7 +274,7 @@
<Update label="June 18, 2025" tags={["Flaky Tests"]}>
**[Flaky Tests: Test suite and class available on test details page](/changelog/2025-06-18-test-suite-and-class-available-on-test-details-page)**

The names of a test’s suite and class are now visible on the test details page of the flaky test dashboard, along with a file search link for repos using either GitHub or Bitbucket as source control…

Check warning on line 277 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L277

Did you really mean 'repos'?
</Update>

<Update label="June 11, 2025" tags={["Flaky Tests"]}>
Expand Down Expand Up @@ -306,7 +312,7 @@
<Update label="May 15, 2025" tags={["Flaky Tests"]}>
**[RSpec Plugin for Ruby repos](/changelog/2025-05-15-rspec-plugin-for-ruby-repos)**

The new Flaky Tests RSpec plugin is the best way to run RSpec tests and upload the results to Trunk.

Check warning on line 315 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L315

Did you really mean 'RSpec'?

Check warning on line 315 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L315

Did you really mean 'RSpec'?
</Update>

<Update label="May 9, 2025" tags={["Web App"]}>
Expand All @@ -318,7 +324,7 @@
<Update label="May 8, 2025" tags={["Merge Queue"]}>
**[Merge Queue: Webhooks on batched PR merges](/changelog/2025-05-08-merge-queue-webhooks-on-batched-pr-merges)**

Webhooks are now available for batched PR merges in Merge Queue. This allows you to build custom automations and respond to events when batching is enabled.

Check warning on line 327 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L327

Did you really mean 'automations'?
</Update>

### April 2025
Expand All @@ -332,13 +338,13 @@
<Update label="April 25, 2025" tags={["Flaky Tests"]}>
**[Flaky Tests: Link Ticket to Test Case API](/changelog/2025-04-25-link-ticket-to-test-case-api)**

Today, we’re introducing a new Link Ticket to Test Case API that allows you to link your existing Linear or Jira tickets to tests in the Flaky Tests dashboard.

Check warning on line 341 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L341

Did you really mean 'Jira'?
</Update>

<Update label="April 17, 2025" tags={["Merge Queue"]}>
**[Merge Queue: updateQueue API](/changelog/2025-04-17-merge-queue-updatequeue-api)**

We’ve added a new updateQueue API to Trunk Merge Queue that enables you to update a Merge Queue’s state.

Check warning on line 347 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L347

Did you really mean 'updateQueue'?
</Update>

<Update label="April 17, 2025" tags={["Flaky Tests"]}>
Expand Down Expand Up @@ -378,7 +384,7 @@
<Update label="February 26, 2025" tags={["Flaky Tests"]}>
**[Flaky Tests: Detailed Jira integration status updates](/changelog/2025-02-26-flaky-tests-detailed-jira-integration-status-updates)**

We have an exciting update for teams using the Flaky Test Jira integration to create and track their tickets.

Check warning on line 387 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L387

Did you really mean 'Jira'?
</Update>

<Update label="February 14, 2025" tags={["Flaky Tests"]}>
Expand All @@ -404,7 +410,7 @@
<Update label="January 29, 2025" tags={["Code Quality"]}>
**[Plugins 1.6.7](/changelog/2025-01-29-plugins-1-6-7)**

New security linter: snyk. Thanks @fsargent for the contribution!; New action: terraform-docs. Thanks @Gowiem for the contribution!.

Check warning on line 413 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L413

Did you really mean 'snyk'?
</Update>

<Update label="January 28, 2025" tags={["Merge Queue"]}>
Expand All @@ -428,13 +434,13 @@
<Update label="January 14, 2025" tags={["Flaky Tests"]}>
**[Flaky Tests: Support for Bazel build event protocol](/changelog/2025-01-14-flaky-tests-support-for-bazel-build-event-protocol)**

Trunk Flaky Tests now supports uploading test results by parsing Bazel Build Event Protocol (BEP) files.

Check warning on line 437 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L437

Did you really mean 'Bazel'?
</Update>

<Update label="January 3, 2025" tags={["Flaky Tests"]}>
**[Flaky Tests: Flaky test detection on merge branches](/changelog/2025-01-03-flaky-tests-flaky-test-detection-on-merge-branches)**

We’re excited to announce improved flaky test detection for merge queue users. In a merge queue, a single flaky failure will force every enqueued PR behind it to be retested, affecting every engineer…

Check warning on line 443 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L443

Did you really mean 'enqueued'?
</Update>


Expand All @@ -451,7 +457,7 @@
<Update label="December 10, 2024" tags={["Code Quality"]}>
**[Plugins 1.6.6](/changelog/2024-12-10-plugins-1-6-6)**

Upgrade ruby-build to 20241105. Thanks @amkisko for the contribution!; Upgrade jdk to 23.

Check warning on line 460 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L460

Did you really mean 'jdk'?
</Update>

### November 2024
Expand All @@ -459,7 +465,7 @@
<Update label="November 13, 2024" tags={["Code Quality"]}>
**[Plugins 1.6.5](/changelog/2024-11-13-plugins-1-6-5)**

Use a hadolint version that works on the latest versions of macOS; Fix parsing in new versions of ruff for source files with syntax errors.

Check warning on line 468 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L468

Did you really mean 'hadolint'?
</Update>

<Update label="November 12, 2024" tags={["Flaky Tests"]}>
Expand Down Expand Up @@ -497,7 +503,7 @@
<Update label="October 28, 2024" tags={["Flaky Tests"]}>
**[Flaky Tests: Improved support for iOS and Swift developers](/changelog/2024-10-28-flaky-tests-improved-support-for-ios-and-swift-developers)**

Flaky Tests now supports the XCResults format outputted by Swift projects using XCTests. You can now upload the .xcresults format to Trunk directly, without configuring a JUnit XML reporter.

Check warning on line 506 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L506

Did you really mean 'XCResults'?

Check warning on line 506 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L506

Did you really mean 'XCTests'?

Check warning on line 506 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L506

Did you really mean 'JUnit'?
</Update>

<Update label="October 17, 2024" tags={["Flaky Tests"]}>
Expand Down Expand Up @@ -535,7 +541,7 @@
<Update label="September 4, 2024" tags={["Code Quality"]}>
**[CLI 1.22.5](/changelog/2024-09-04-cli-1-22-5)**

Help text improvements; trunk fmt will now use configured verbs when presenting results to the user.

Check warning on line 544 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L544

Did you really mean 'fmt'?
</Update>

### August 2024
Expand All @@ -543,7 +549,7 @@
<Update label="August 27, 2024" tags={["Flaky Tests"]}>
**[Flaky Tests: Jira Integration](/changelog/2024-08-27-flaky-tests-jira-integration)**

We’re excited to announce the latest enhancement: Jira integration for managing flaky tests. This update builds on our MVP by streamlining the issue management process within Jira.

Check warning on line 552 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L552

Did you really mean 'Jira'?

Check warning on line 552 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L552

Did you really mean 'Jira'?
</Update>

<Update label="August 20, 2024" tags={["Code Quality"]}>
Expand Down Expand Up @@ -575,7 +581,7 @@
<Update label="July 16, 2024" tags={["Code Quality"]}>
**[Plugins 1.6.1](/changelog/2024-07-16-plugins-1-6-1)**

Support additional osv-scanner lockfile types; Added tfvars filetype.

Check warning on line 584 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L584

Did you really mean 'lockfile'?

Check warning on line 584 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L584

Did you really mean 'tfvars'?

Check warning on line 584 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L584

Did you really mean 'filetype'?
</Update>

<Update label="July 15, 2024" tags={["Flaky Tests"]}>
Expand Down Expand Up @@ -647,7 +653,7 @@
<Update label="April 24, 2024" tags={["Code Quality"]}>
**[Plugins 1.5.0](/changelog/2024-04-24-plugins-1-5-0)**

New runtime: php; New linter and tool: tofu.

Check warning on line 656 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L656

Did you really mean 'php'?
</Update>

<Update label="April 23, 2024" tags={["Code Quality"]}>
Expand All @@ -671,7 +677,7 @@
<Update label="April 5, 2024" tags={["Merge Queue"]}>
**[Merge Queue: Webhook support](/changelog/2024-04-05-merge-web-hook-support)**

Trunk Merge Queue now supports webhooks to provide realtime events to integrated platforms. See the Webhooks API doc for more details.

Check warning on line 680 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L680

Did you really mean 'realtime'?
</Update>

### March 2024
Expand Down Expand Up @@ -709,7 +715,7 @@
<Update label="March 1, 2024" tags={["Code Quality"]}>
**[Plugins 1.4.4](/changelog/2024-03-01-plugins-1-4-4)**

New linter and formatter: psscriptanalyzer. Thanks @natescherer for the contribution!; New tool: kubectl.

Check warning on line 718 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L718

Did you really mean 'psscriptanalyzer'?
</Update>

### February 2024
Expand All @@ -735,7 +741,7 @@
<Update label="February 16, 2024" tags={["Code Quality"]}>
**[Plugins 1.4.3](/changelog/2024-02-16-plugins-1-4-3)**

Add support for Ruff formatting; Add support for commitizen. Thanks @natescherer for the contribution!.

Check warning on line 744 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L744

Did you really mean 'commitizen'?
</Update>

<Update label="February 15, 2024" tags={["Code Quality"]}>
Expand Down Expand Up @@ -802,7 +808,7 @@
<Update label="December 5, 2023" tags={["Code Quality"]}>
**[CLI 1.18.0](/changelog/2023-12-05-cli-1-18-0)**

Announcing Trunk shell-hooks: Watches your current working directory to ensure that Trunk-managed tools, linters, and runtimes are available in PATH.

Check warning on line 811 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L811

Did you really mean 'runtimes'?
</Update>

<Update label="December 1, 2023" tags={["Code Quality"]}>
Expand All @@ -822,7 +828,7 @@
<Update label="November 20, 2023" tags={["Code Quality"]}>
**[Plugins 1.3.0](/changelog/2023-11-20-plugins-1-3-0)**

New tools: gulp, tailwindcss, tsc, webpack.; New formatter: dotnet-format (MacOS support coming soon).

Check warning on line 831 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L831

Did you really mean 'tailwindcss'?

Check warning on line 831 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L831

Did you really mean 'tsc'?
</Update>

<Update label="November 20, 2023" tags={["Code Quality"]}>
Expand Down Expand Up @@ -878,7 +884,7 @@
<Update label="October 12, 2023" tags={["Code Quality"]}>
**[VSCode 3.5.0](/changelog/2023-10-12-vscode-3-5-0)**

Re-added the ability to format files from tree view navigation menus; Added the ability to autofix issues from the tree view navigation menus.

Check warning on line 887 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L887

Did you really mean 'autofix'?
</Update>

### September 2023
Expand All @@ -886,7 +892,7 @@
<Update label="September 29, 2023" tags={["Code Quality"]}>
**[Plugins 1.2.5](/changelog/2023-09-29-plugins-1-2-5)**

Update svgo to use new fixverb / fixprompt support.

Check warning on line 895 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L895

Did you really mean 'svgo'?

Check warning on line 895 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L895

Did you really mean 'fixverb'?

Check warning on line 895 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L895

Did you really mean 'fixprompt'?
</Update>

<Update label="September 29, 2023" tags={["Code Quality"]}>
Expand All @@ -904,13 +910,13 @@
<Update label="September 26, 2023" tags={["Code Quality"]}>
**[CLI 1.16.1](/changelog/2023-09-26-1-16-1)**

Oxipng now uses the language \"unoptimized image\" rather than \"unformatted file.\"; Improved crash reporting for internal errors.

Check warning on line 913 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L913

Did you really mean 'Oxipng'?

Check warning on line 913 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L913

Did you really mean 'unoptimized'?

Check warning on line 913 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L913

Did you really mean 'unformatted'?
</Update>

<Update label="September 26, 2023" tags={["Code Quality"]}>
**[Plugins 1.2.4](/changelog/2023-09-26-plugins-1-2-4)**

New tool: clangd.

Check warning on line 919 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L919

Did you really mean 'clangd'?
</Update>

<Update label="September 26, 2023" tags={["Code Quality"]}>
Expand All @@ -934,7 +940,7 @@
<Update label="September 13, 2023" tags={["Code Quality"]}>
**[VSCode 3.4.7](/changelog/2023-09-13-vscode-3-4-7)**

Removed some special handling for recycling Webviews; On Windows, show a message indicating that a user has opened a directory that is not a git repository when applicable.

Check warning on line 943 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L943

Did you really mean 'Webviews'?
</Update>

<Update label="September 7, 2023" tags={["Code Quality"]}>
Expand All @@ -960,7 +966,7 @@
<Update label="August 23, 2023" tags={["Code Quality"]}>
**[Plugins 1.2.2](/changelog/2023-08-23-plugins-1-2-2)**

New tool: awscli.

Check warning on line 969 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L969

Did you really mean 'awscli'?
</Update>

<Update label="August 22, 2023" tags={["Code Quality"]}>
Expand Down Expand Up @@ -1002,5 +1008,5 @@
<Update label="August 1, 2023" tags={["Code Quality"]}>
**[Plugins 1.1.0](/changelog/2023-08-01-plugins-1-1-0)**

New security linter: dustilock; New security linter: trufflehog-git (a variant of trufflehog).

Check warning on line 1011 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L1011

Did you really mean 'dustilock'?

Check warning on line 1011 in changelog/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

changelog/index.mdx#L1011

Did you really mean 'trufflehog'?
</Update>
1 change: 1 addition & 0 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -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-failure-count-monitor",
"changelog/2026-05-18-flaky-tests-monitor-label-actions",
"changelog/2026-05-18-flaky-tests-test-labels",
Expand Down
6 changes: 6 additions & 0 deletions merge-queue/changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@
Automatic bot comment hiding, a skip-batching toggle, and Celebration Mode come to the Trunk for GitHub Chrome Extension.
</Update>

<Update label="May 19, 2026" tags={["Merge Queue"]}>
**[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.
</Update>

### April 2026

<Update label="April 30, 2026" tags={["Merge Queue"]}>
Expand Down Expand Up @@ -45,7 +51,7 @@
<Update label="March 25, 2026" tags={["Merge Queue"]}>
**[Merge Queue: Multiple Queues Per Repo with Grouped Selector](/changelog/2026-03-25-merge-queue-multiple-queues-per-repo-with-grouped-selector)**

Previously, a repo could only have one queue. Now you can create additional queues from the merge queue creation page. The repo selector shows repos that already have queues and how many exist.

Check warning on line 54 in merge-queue/changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/changelog.mdx#L54

Did you really mean 'repos'?
</Update>

<Update label="March 25, 2026" tags={["Merge Queue"]}>
Expand Down Expand Up @@ -150,7 +156,7 @@
<Update label="May 8, 2025" tags={["Merge Queue"]}>
**[Merge Queue: Webhooks on batched PR merges](/changelog/2025-05-08-merge-queue-webhooks-on-batched-pr-merges)**

Webhooks are now available for batched PR merges in Merge Queue. This allows you to build custom automations and respond to events when batching is enabled.

Check warning on line 159 in merge-queue/changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/changelog.mdx#L159

Did you really mean 'automations'?
</Update>

### April 2025
Expand All @@ -158,7 +164,7 @@
<Update label="April 17, 2025" tags={["Merge Queue"]}>
**[Merge Queue: updateQueue API](/changelog/2025-04-17-merge-queue-updatequeue-api)**

We’ve added a new updateQueue API to Trunk Merge Queue that enables you to update a Merge Queue’s state.

Check warning on line 167 in merge-queue/changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/changelog.mdx#L167

Did you really mean 'updateQueue'?
</Update>

### January 2025
Expand Down Expand Up @@ -211,7 +217,7 @@
<Update label="April 5, 2024" tags={["Merge Queue"]}>
**[Merge Queue: Webhook support](/changelog/2024-04-05-merge-web-hook-support)**

Trunk Merge Queue now supports webhooks to provide realtime events to integrated platforms. See the Webhooks API doc for more details.

Check warning on line 220 in merge-queue/changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/changelog.mdx#L220

Did you really mean 'realtime'?
</Update>

### March 2024
Expand Down
23 changes: 23 additions & 0 deletions merge-queue/using-the-queue/reference.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,15 +24,38 @@
- **Submit:** `/trunk merge`
- **Cancel:** `/trunk cancel`
</Tab>
<Tab title="GitHub Label">
Apply a configured **enqueue label** to the pull request on GitHub to submit it automatically. See [Enqueueing by label](#enqueueing-by-label) below.

Check warning on line 28 in merge-queue/using-the-queue/reference.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/using-the-queue/reference.mdx#L28

Did you really mean 'Enqueueing'?
</Tab>
</Tabs>

## Enqueueing by label

Check warning on line 32 in merge-queue/using-the-queue/reference.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/using-the-queue/reference.mdx#L32

Did you really mean 'Enqueueing'?

You can configure a GitHub label that, when applied to a pull request, automatically submits it to the merge queue. This lets teams integrate Trunk Merge Queue into existing label-based GitHub workflows and automations without requiring a comment or CLI command.

Check warning on line 34 in merge-queue/using-the-queue/reference.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/using-the-queue/reference.mdx#L34

Did you really mean 'automations'?

### Configure the enqueue label

1. Navigate to **Settings** > **Repositories** > **Merge Queue**.
2. Under **Enqueue by label**, enter the name of the GitHub label you want to use (for example, `merge-queue` or `ready-to-merge`).
3. Save the setting.

Once configured, applying that label to any open pull request in the repository will enqueue it automatically. Trunk removes the label from the PR once the queue picks it up.

<Info>
The enqueue label only triggers enqueueing when applied to an open PR that is eligible for the queue. PRs that are draft, failing required checks, or otherwise ineligible will not be enqueued.

Check warning on line 45 in merge-queue/using-the-queue/reference.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/using-the-queue/reference.mdx#L45

Did you really mean 'enqueueing'?

Check warning on line 45 in merge-queue/using-the-queue/reference.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/using-the-queue/reference.mdx#L45

Did you really mean 'enqueued'?
</Info>

### Removing from the queue

Removing the configured label from a PR does **not** cancel it from the queue. Use `/trunk cancel`, the Web App, or the CLI to cancel an in-progress PR.

## Pull request processing

Once a PR is submitted to the merge queue it goes through several states. First, it starts as _Queued_ until all of the required conditions to submit it are met. Once ready, the PR moves to the _Pending_ state, waiting for a Merge Queue to pick it up, and then enters the _Testing_ state. Once the tests pass the PR may still need to wait for upstream PRs. Once any upstream PRs are complete the PR will be merged and then removed from the Merge Queue. If a PR fails or is canceled then it will go to the failed or canceled state.

## Pull request states

A PR's lifecycle in the Merge Queue goes through the following states:

Check warning on line 58 in merge-queue/using-the-queue/reference.mdx

View check run for this annotation

Mintlify / Mintlify Validation (trunk-4cab4936) - vale-spellcheck

merge-queue/using-the-queue/reference.mdx#L58

Did you really mean 'PR's'?

| State | Description |
| --- | --- |
Expand Down
Loading