Submit and cancel pull requests

Covers the journey of a PR from submission through various states to completion

Submitting and cancelling pull requests

Chrome Extension

Install the Trunk for GitHub Chrome Extension to submit and cancel PRs directly from GitHub without leaving your pull request page.

State	Description
Submit	Click “Add to Merge Queue” button. You can change the priority of the submission by clicking on the drop-down arrow.
Pending	Click “Remove” to remove the PR from the queue.

GitHub Comment

Post a comment directly on the pull request:

• Submit: /trunk merge
• Cancel: /trunk cancel

GitHub Label

Apply a configured enqueue label to the pull request on GitHub to submit it automatically. See 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 Merge Queue → [your repository] → Settings.
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 dequeues it from the merge queue. You can also 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:

State	Description
Queued	The PR was submitted to Trunk Merge Queue, but the PR isn’t eligible for merging yet. Impacted targets may not be uploaded, or readiness checks may not have passed.
Pending	The MergeGraph created a node for the PR. Testing will begin if the graph has capacity.
Testing	The PR is testing. Required status checks that Trunk Merge Queue must gate on before merging PRs can be specified with in .trunk/trunk.yaml or through GitHub branch protection rules as the “Status checks that are required” before merging on your merge branch
Tests Passed	The PR successfully passed tests. It may have to wait for upstream PRs to complete tests before merging.
Pending Failure	The PR failed tests. The cause of failures is still indeterminate - it may be due to an upstream PR, or due to the current PR. It will wait until the root cause of tests has been determined, and restart testing on your PR if due to an upstream PR. If you want to manually restart a failed PR, see manually restarting PRs.
Merged	The PR successfully merged into the target branch. It will be removed from the queue.
Failed	The PR caused a testing failure. It will be removed from the queue.
Cancelled	The PR was cancelled, e.g. /trunk cancel. It will be removed from the queue.