# GitHub Stacked PRs Hacker Approved page: https://hackerapproved.com/p/github-stacked-prs/ 36 people recommended GitHub Stacked PRs in Hacker News comments, 26 had mixed feelings and 59 criticized it, November 2025 to October 2026. It was recommended in 3 of 12 months, in 3 threads. It does not meet the Hacker Approved badge rule. 22 of the 36 people who recommend it commented in one thread, “GitHub Stacked PRs”. **Verdict:** More people criticize it than recommend it. People like its built-in stack view and one-step landing for reviewing large changes. Critics say it skips rebasing and reordering, and lock-in. Summary written by Claude from the comments below. ## What people warn about - Rebasing and reordering not handled (3 comments in the sample): "GitHub stacked PRs solve none of my problems. Stacked PRs doesn't take care of the reordering of commits, it doesn't take care of rebasing changes" ([source](https://news.ycombinator.com/item?id=49115302)) "all the others (ime) seem to not cleanly rebase on main. They end up with conflicts that require manual fixing" ([source](https://news.ycombinator.com/item?id=49122236)) "Only complaint I had was that `gh stack rebase` was struggling rebasing after squash merges" ([source](https://news.ycombinator.com/item?id=49113201)) - Developers must still split PRs (2 comments in the sample): "It's good to have this feature, but it is still up to the individual developers to separate the PR work" ([source](https://news.ycombinator.com/item?id=49115431)) "those who’ve forgotten that they should be splitting changes into multiple logical commits inside a PR" ([source](https://news.ycombinator.com/item?id=49120511)) ## Why people recommend it - Smaller reviewable units ease review (3 comments in the sample): "Stacked PRs are superior here because they eliminate that extra work of the draft PR and parallelize the review process slightly better." ([source](https://news.ycombinator.com/item?id=47767197)) "It’s useful for large PRs in large repos with many contributors. It reduces the burden for reviewers." ([source](https://news.ycombinator.com/item?id=47760402)) "stacking is such a better ux for separating out a feature diff into distinct component units" ([source](https://news.ycombinator.com/item?id=49113349)) - Native UI for managing PR chains (3 comments in the sample): "There seems to be a native stack navigation widget on the PR page, which is certainly a welcome addition" ([source](https://news.ycombinator.com/item?id=47758173)) "in the UI if you base a PR on another branch you can just check a box to make it a stack" ([source](https://news.ycombinator.com/item?id=47758136)) "this gives you a UI to manage the PRs of the multiple tickets" ([source](https://news.ycombinator.com/item?id=49120770)) - Handles PR bookkeeping for series (3 comments in the sample): "Stacked PRs track changes through updates and can be integrated progressively as they get validated." ([source](https://news.ycombinator.com/item?id=47758101)) "multiple PRs gives you the tools to manage the commits properly which GitHub is missing" ([source](https://news.ycombinator.com/item?id=47757900)) "it just takes care of the bookkeeping to associate the series of smaller PRs" ([source](https://news.ycombinator.com/item?id=47764786)) - Lands whole stack together (2 comments in the sample): "What is actually useful with natively supported stacks is if you can land the entire stack together and only do 1 CI/actions run." ([source](https://news.ycombinator.com/item?id=47759752)) "The great part is you can land multiple PRs in one atomic operation" ([source](https://news.ycombinator.com/item?id=49116393)) ## Other code review tools people recommend - [Gerrit](https://hackerapproved.com/p/gerrit/): 44 recommend, 11 mixed, 11 criticize - [Graphite code review](https://hackerapproved.com/p/graphite/): 35 recommend, 7 mixed, 13 criticize - [CodeRabbit](https://hackerapproved.com/p/coderabbit/): 28 recommend, 4 mixed, 29 criticize - [Sashiko](https://hackerapproved.com/p/sashiko/): 10 recommend, 3 mixed, 3 criticize ## The badge A product earns the Hacker Approved badge when at least 10 people recommend it, recommenders outnumber critics at least 2 to 1 (mixed feelings count toward neither side), it was recommended in at least 4 of the 12 months and in at least 5 different threads, and no single thread supplies more than half of the people who recommend it. Health and money products are never badged. ## Cite as Hacker Approved, "GitHub Stacked PRs", https://hackerapproved.com/p/github-stacked-prs/ (36 recommend, 26 mixed, 59 criticize; Hacker News comments, November 2025 to October 2026). Counts updated 2 Nov 2026, with data through October 31, 2026.