Use case
The change nobody wants to review
A framework upgrade touching two hundred files gets one approval and no comments. Everyone knows that approval means nothing.
Split it, without losing the thread
A stack turns one unreviewable change into a sequence of reviewable ones that still merge in order. Each pull request diffs against its parent, so reviewing the fourth means reading the fourth, not the first three again.
The mechanical parts get out of the way
- Generated files and lockfiles start collapsed, with their counts still visible
- Whitespace-only changes hide behind a toggle, so a reformat does not bury the logic
- Renames and copies are detected by git rather than guessed from the path
- A file over five hundred changed lines starts collapsed rather than dominating the page
It stays fast when it gets big
Diffs are rendered on the server. The browser receives HTML rather than a diff library and a payload to assemble, which is why a hundred files stays a long page instead of a hung tab.
Merging the stack
Merge the bottom and everything above it retargets automatically. A child that was pointed elsewhere by hand keeps its base and simply loses the stale link.
Review the refactor properly
The tools that make a large diff readable are the default here, not a setting.