Reduced time to flake detection

Configure independent detection monitors (threshold, pass-on-retry, and manual) with adjustable sensitivity and recovery periods to match your team's flake tolerance.
Read the docs

When a high percentage of tests fail in a single run, treat it as an infrastructure failure rather than individual test failures
Read the docs

Mute, delete, and manually flag individual test monitors to control how tests are tracked and when alerts fire.
Read the docs

View a timeline of recent test runs including pass/fail results, quarantine status, and status changes to understand how a test has behaved over time.

Add labels to tests and filter for them in the app.
Read the docs

Support agentic flows to autofix failing tests on PRs
Read the docs

Test case monitors can manage test case labels.
Read the docs

Flag tests as flaky or broken when they hit a configured number of failures in a rolling window, even when the failure rate alone wouldn't trigger detection.
Read the docs

Track timing and reliability of GitHub Actions jobs and trigger alerts

Collections let you organize tests into logical groups (framework, application, etc) so you can configure detection rules and thresholds independently for each. Whether your Jest unit tests need stricter flake detection than your Playwright E2E suite, or different teams want their own reporting views, Collections give you the flexibility to match your CI reliability strategy to how your codebase is actually structured.

Dispatch an AI agent to fix flaky tests as they're detected

Dynamically Skip CI Jobs based on PR content, job history, etc.

Revised REST API for better lookups and modifications to tests and monitors.

Configure monitors to detect and label new tests, skipped tests, and slow tests.
Read the docs

Filter merge queue health metrics by impacted targets to analyze performance for specific parts of your codebase
Read the docs

Merge queue dashboard pages support updating automatically in real-time

Receive personalized Slack DMs about your PRs' progress through the merge queue
Read the docs

Mark specific PRs to test individually without batching, ensuring if they fail, they don't take down other PRs with them
Read the docs

Run independent merge queues for different branches in the same repository

Skip redundant testing and merge immediately when your PR is already up-to-date and the queue is empty
Read the docs

Select preferred merge method (squash, rebase, merge) for your PRs going through the merge queue
Read the docs

Reuse CI Job results when isolating failures in batched PRs to save CI resources
Read the docs

Set higher test concurrency for failure isolation without slowing down your main merge queue
Read the docs

Add an endpoint to allow users to scrape merge queue metrics for monitoring
Read the docs

Programmatically create, configure, and manage merge queues via REST API
Read the docs

Support for merging stacked PRs atomically
Read the docs

Heavily improve what Merge Queue does in the event of a code merge conflict being encountered when submitting a PR to the queue. This will make it easier for developers to respond to encountering a merge conflict.

Control your Trunk Merge Queue through Terraform
Read the docs

Support seamless integration with both GitHub rulesets and classical branch protection rules
Read the docs

Bring more Merge Queue functionality right into GitHub's UI
Read the docs

Allow users to force a PR to be admitted into the Merge Queue before it becomes mergeable, after which Merge Queue will merge the PR if it passes tests in the MQ, effectively bypassing GH branch protections
Read the docs

Drill down from any point on the Merge Queue Health charts to a sortable list of the pull requests that make up that data.
Read the docs

We're building first-class support for deploying Trunk Merge Queue's data plane directly into your AWS account. For teams with strict data residency, compliance, or on-prem GitHub Enterprise requirements, you'll soon be able to run the Merge Queue entirely within your own infrastructure while we continue to manage the control plane, giving you enterprise-grade security and control without sacrificing the fully managed experience

Trigger alerts on metrics like failure rate or expected time to merge

Configure trusted authors whose commits won't force queued PRs to restart testing

Merge Queue will make it clear if anything about your current GitHub branch protection rules will interfere with Merge Queue working

Allow submitting and removing PRs to Trunk Merge Queue via applying and removing custom labels to the PR. This adds an additional way to submit the PR to the merge queue - see https://docs.trunk.io/merge-queue/using-the-queue/reference#submitting-and-cancelling-pull-requests.