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

Reduced time to flake detection

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

Full customization over flake detection rules

Track timing and reliability of GitHub Actions jobs and trigger alerts

Trigger an Agent to investigate and fix build failures

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

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

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

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

Merge queue dashboard pages support updating automatically in real-time

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

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

Run independent merge queues for different branches in the same repository

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

AI Agent for automatically resolving test failures and re-submitting PRs

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

Support for merging stacked PRs atomically

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