feat(replay): group meaningful source-backed changes - #165
Merged
Conversation
fcoury
force-pushed
the
fcoury/pr-replay-semantic-changes
branch
from
July 30, 2026 19:40
5d76152 to
17d2db0
Compare
fcoury
force-pushed
the
fcoury/pr-replay-semantic-changes
branch
from
July 30, 2026 22:11
17d2db0 to
5298c15
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Raw Git hunks are not always meaningful review steps. A standalone blank-line hunk can inherit the name of a neighboring function, while a larger compatibility change can be reduced to its first added field and receive an unrelated pull-request summary. That makes PR Replay harder to trust precisely when reviewers are trying to understand what the original code actually does.
What changed
How to Test
Space R g. Confirm the blank line is not presented as an independent named change, the substantive change remains accurately named, and its original diff still includes both exact hunks.WHYand bounded supporting details rather than describing only the first field.a, and confirm every displayed original hunk applies together. Pressuand confirm the complete group reverts in one undo without overwriting reviewer-authored changes.--resume, and confirm its progress, original source anchors, and single-step undo are restored.cargo test --libandcargo clippy --all-targets --all-features -- -D warnings.