enhance: file rename detection and path resolution in file history#1372
Closed
gadfly3173 wants to merge 5 commits into
Closed
enhance: file rename detection and path resolution in file history#1372gadfly3173 wants to merge 5 commits into
gadfly3173 wants to merge 5 commits into
Conversation
Collaborator
|
not planned to do this in file history. |
Contributor
Author
|
I think this is a very common capability in various git GUI clients. e.g.
|
gadfly3173
force-pushed
the
fix/file-rename
branch
from
f67a051 to
409ca38
Compare
Contributor
|
@gadfly3173 - This PR contains lots of commits from the |
Contributor
@love-linger Should this PR have the |
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
3 participants
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.
No description provided.