[Git Formats] Diff TOC components for renames #4196
Conversation
This file contains 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
michaelblyons
changed the title
michaelblyons
force-pushed
the
git/diff/toc-changes
branch
from
7b7d37b to
1f6bf7f
Compare
|
Branching would also be an option. Maybe not worth it. |
deathaxe
reviewed
Mar 28, 2025
|
I am fine with not pushing contexts for braces. |
Co-authored-by: deathaxe <[email protected]>
deathaxe
previously approved these changes
Mar 28, 2025
michaelblyons
commented
Mar 28, 2025
deathaxe
approved these changes
Mar 30, 2025
jrappen
approved these changes
Mar 30, 2025
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.
Adds scopes to some additional sections of the rename/move/copy format.
If the community determines that it's worth it to forward-lookahead open/close brace pairs, I can do that. But sometimes they are not matched, as in the example test.