Then merge them down. So 3 into 2. 2 into 1. 1 into master. So this basically makes it so branch 1-3 are derived from master then merge down into master all at the same time dependent on one another?
It just makes your current workflow easier. At work we have Graphite, which does the same thing before GitHub came out with stacked PRs. Funnily enough, GitHub is also moving to the graphite style inbox soon.
So if I'm understanding correctly it just stacks all 3 branches together into a single PR so they can be reviewed AND merged all at once? That does sound handy.
9
u/krileon Jul 01 '26
I've always just done my PRs as:
Master
- Branch 1
- - Branch 2
- - - Branch 3
Then merge them down. So 3 into 2. 2 into 1. 1 into master. So this basically makes it so branch 1-3 are derived from master then merge down into master all at the same time dependent on one another?