News for hackers. Stuff that matters.
Re:Stacked PRs are now live on GitHub by dml2135 on Friday July 31, 2026 @01:54PM (#49126462)
I didn't see the appeal of bespoke PR stacking tools when it was the headline feature of Graphite, and I still don't see it now.

Stacking PRs is useful, but I haven't encountered issues with the ergonomics of just using normal git operations to do it. My stacking workflow is roughly:

- Open the first PR from `branch-1` against `main`

- While waiting for a review on that first PR, if I need to build on subsequent work in `branch-1`, I'll `git checkout -b branch-2`, and open a draft PR against `branch-1`

- If the open review requires me to make changes to make changes to `branch-1`, I'll `git merge branch-1` on `branch-2` to pull them up the stack

- After `branch-1` is merged, my draft PR for `branch-2` will automatically update to being opened against `main`

- Repeat as necessary depending on how much stacking is requires and how far ahead I get against my reviewers

I don't find any of this all that difficult or cumbersome. Is there something that this feature offers, that I'm missing out on?

Re:Stacked PRs are now live on GitHub by lukaszkorecki on Friday July 31, 2026 @06:25PM (#49129220)
That's how I worked but it gets tedious for reviewers because there's no easy way to navigate the stack. In the end, I vibe coded an internal PR stacker which stores stack data using `git notes` (allowing multiple people to work in a stack) and updates PR description with stack navigation. It uses merge, rather than rebase because history is not that important (final code is).