fix(core): handle file renames properly for affected #15340
Merged
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.
Current Behavior
Moving a file only affects the project it is moved to. This is because the underlying command to get the changed set of files does not include it:
Expected Behavior
Moving files affects both the project the file was moved to as well as the project the file was moved from. This is done by using the
--no-renames
flag. This will prevent git from collapsing the to and from file paths.Related Issue(s)
Fixes #13677