Engineers Hate Slow Merge Queues. We can help.
Try Trunk Merge Queue and See Faster Merges Today
Run unrelated changes through CI at the same time. Thanks to built-in support for tools like Nx and Bazel, Trunk Merge Queue groups and tests related PRs in a single queue while unrelated PRs are run in parallel.
Learn more about Parallel Queues→
60%
improvement in turnaround time.
1.92x
improvement in keeping mainline green.
94%
of developers rated the merge queue as better than previous systems.
Trunk's parallel merge queues provide speedy PR merging with all the protection of a traditional merge queue
Protect Your Main Branch. Trunk Merge strategically tests combinations of pull requests to identify issues before they merge into your main branch.
"Potential problems are resolved before we even commit our code. That's a big win for any team."
David Mytton
CEO at Arcjet
Integrate with your Build System. Use data from build systems like Bazel or Nx to run CI jobs for unrelated PRs in parallel queues.
Real-time notifications. Get updates on any platform using webhooks or the built-in Slack integration, and find the latest info in automated GitHub PR comments.
Break the Logjam. Escape O(n²) CI runtime and only test your PR against other relevant changes, instead of every PR in the queue.
"With Trunk Merge Queue, I've helped enable many aspects of our development process that would've been otherwise challenging. Now, we can easily handle a high volume of changes without compromising on stability."
Benjamin Cool
Developer Experience Lead at Cavnue
Merge Automation. Trunk Merge Queue will wait until all the gating requirements are met before merging so you can avoid context switching to merge at a later time.
Always Up-to-Date CI. Merge Queue ensures every PR is tested against the latest commit on your main branch so you can skip manual rebases and avoid testing against out-of-date code.
Highly Customizable Merge Queue. Use the public REST API to submit PRs for testing and merging, cancel them, and access status info to fine-tune the queue.
"Trunk has saved us 330 hours by preventing merge issues over the last 35 days - that's 9.4 hours of engineering productivity saved per day...it's been great."
Faire reduced main branch failures and saved 18.8 hours of daily engineering time using Trunk Merge and Check. By automating merges and improving CI efficiency, they stabilized workflows, improved code quality, and freed engineers to focus on higher priority work.
George Jacob
Making Developer Lives Better @ Faire
Glydways faced long wait times for merges, high CI costs, and bottlenecks due to outdated branches and limited resources. By adopting Trunk Merge Queue, they sped up merges, optimized CI resource use, and introduced features like priority merging for critical changes.
Juan Ortega
Technical Lead Manager @ GlydwaysTrunk is a merge queue for GitHub repos, and it works with any CI or build provider including Jenkins, GH Actions, CircleCI, Buildkite, Bazel, Nx, and more.
