← use cases · merge queue
A CI-gated agent merge queue
Let agents propose branches all day, and land only the ones that pass your existing CI, in order.
who it's for
Teams where multiple agents (and humans) are producing branches faster than anyone can review and merge them safely.
the problem
Whichever branch you rebase first wins is not a merge strategy. When a fleet of agents is opening branches, you need an ordered queue that runs your gates and lands work deterministically.
how brat does it
- 1
Point the Refinery at your existing CI — brat integrates with it, it does not replace it.
- 2
Configure the merge policy once: rebase, squash, or merge.
- 3
Agent branches enter the queue as tasks reach merged state; the Refinery processes them in order.
- 4
Anything that fails CI stays out; the failure is an event you can inspect, not a silent drop.
the outcome
The chaos of a dozen concurrent branches becomes an ordered, CI-gated queue — the same discipline a human merge queue gives you, applied to an agent fleet.