Seonglae Cho- When there are many small changes
- When the team wants to move quickly
Stacked Diff Tools
코드 리뷰의 또 다른 접근 방법: Pull Requests vs. Stacked Changes
인프콘 2022에서 나눈 Stacked Changes 이야기 입니다. https://infcon.day/speaker/%ec%84%9c%ec%a7%80%ec%97%b0-%ec%bd%94%eb%93%9c%eb%a6%ac%eb%b7%b0-%ea%b9%83%ed%97%99/
https://www.slideshare.net/JiyeonSeo2/pull-requests-vs-stacked-changes
Github plan
An extension that officially supports PR dependencies and automatic merge flows (merge queue.)
Jared Palmer on Twitter / X
RE: Stacked Diffs on @GitHub After discussion w @ttaylorr_b, we can implement stacked PRs/PR groups already (in fact we kind of do with Copilot) but restacking (automatically fanning out changes from the bottom of the the stack upwards) would be wildly inefficient. To do it… https://t.co/HedXhsYR72— Jared Palmer (@jaredpalmer) October 21, 2025
https://x.com/jaredpalmer/status/1980619222918262842
Stacked PR
In praise of the stacked pull request | Swizec Teller
How fast you do code review is how fast you do everything. Your PR queue is the leading indicator of team velocity. Stacked PRs can help.
https://swizec.com/blog/in-praise-of-the-stacked-pull-request/
