Engineers Hate Slow Merge Queues. We can help.
Try Trunk Merge Queue and See Faster Merges Today
Your merge queue should know that not all code changes are interrelated! Parallel Queues, PRs only test with related changes - so your workflow speeds up, and your docs never have to wait for service code adjustments.
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
Build System Integration. Integrating with any build system, Trunk Merge dynamically creates parallel queues so unrelated PRs can merge simultaneously, making it far faster than a traditional merge queue.
Get updated wherever you work. Trunk integrates with any communication platform your team uses.
Break the Logjam. Escape O(n²) by only testing your PR against other relevant PRs, not 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. Queue your PR to be merged with Trunk Merge, and it will wait until all the gating requirements are met before merging, letting you avoid context switching to merge it later.
Always Up-to-Date CI. Don’t worry about the freshness of your CI results; Merge ensures that every PR is tested against the latest commit on your main branch.
Highly Customizable Merge Queue. Our public API provides access to submit PRs for testing and merging, canceling PRs, and providing extra information to optimize 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
Engineering Manager @ 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
Engineering Manager @ FaireTrunk 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.
