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..4577f4a1
--- /dev/null
+++ b/changelog/2026-05-19-merge-queue-enqueue-by-label.mdx
@@ -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.
+
+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.
+
+
+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 be480ef8..691b49c3 100644
--- a/changelog/index.mdx
+++ b/changelog/index.mdx
@@ -14,6 +14,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: Failure Count Monitor](/changelog/2026-05-18-flaky-tests-failure-count-monitor)**
diff --git a/docs.json b/docs.json
index 5288c149..91ded982 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-failure-count-monitor",
"changelog/2026-05-18-flaky-tests-monitor-label-actions",
"changelog/2026-05-18-flaky-tests-test-labels",
diff --git a/merge-queue/changelog.mdx b/merge-queue/changelog.mdx
index e27b9bb6..dd0518d4 100644
--- a/merge-queue/changelog.mdx
+++ b/merge-queue/changelog.mdx
@@ -14,6 +14,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
diff --git a/merge-queue/using-the-queue/reference.mdx b/merge-queue/using-the-queue/reference.mdx
index 24e0e7fd..07890b1d 100644
--- a/merge-queue/using-the-queue/reference.mdx
+++ b/merge-queue/using-the-queue/reference.mdx
@@ -24,8 +24,31 @@ description: "Covers the journey of a PR from submission through various states
- **Submit:** `/trunk merge`
- **Cancel:** `/trunk cancel`
+
+ Apply a configured **enqueue label** to the pull request on GitHub to submit it automatically. See [Enqueueing by label](#enqueueing-by-label) below.
+
+## Enqueueing by label
+
+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.
+
+### 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.
+
+
+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.
+
+
+### 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.