productcode & review
rbs stack submit
Review small changes that land in order. Nothing waits on a 2,000-line diff.
Split the work into a stack of branches. Each gets its own review, the hub shows where it sits in the stack, and sync lands what merged and restacks the rest.
how you use it
Stacked changes, in order.
01
Split as you go
Start the next branch on top of the current one and keep working. The parent is stored in git itself, under refs/branch-metadata, in the same shape Graphite uses, so a clone carries the stack and no service has to remember it.
02
Submit: one change request per branch
Submit pushes the stack and opens or updates a change request for each branch. The review page reads the stack from git, shows “2 of 2”, links the neighbours, and offers the whole chain as markdown to paste anywhere.
03
The agent’s loop: a stack per task, reviews that stay honest
An agent builds its task as a stack too, and submits it the same way. Approvals pin to the commit they judged, so when the agent pushes again after a review, the approval reads outdated and the reviewer sees exactly what changed since. Threads on a superseded commit collapse, because stacking force-pushes constantly.
- SCSarah Chen Approved2h
04
Land in order
A fix that belongs three branches down goes there with absorb, and everything above is restacked. Sync pulls trunk, deletes what landed and restacks what is left, keeping the reviews that still apply. Three 200-line reviews get read today; one 600-line review waits for Friday.
not built yet: a merge queue; a stack lands one branch at a time from the review page · squash and rebase merge options
The full reference lives in the docs.
works with
Open a branch and try it.
Boots in seconds. Your team joins with a link.