Fix: Handle case when files are moved/renamed in the git history #5
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
…lity Feature: Ignore files matching patterns with `.gitignore`
…, main.rs is clean again
…lity Refactor file utilities into file_utils, minor refactor with tests…
… which were moved/renamed
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.
Need to cleanup this branch thoughDoneSince the git history can also have details about deleted file, the temporary (but also reasonable) solution would be to skip those files. In the future, it would be ideal to show those files but inform the user that they were deleted/renamed/moved. On the plugins side, it would be nice to let user open the telescope file search from there (neovim) and on VSCode (open file search prompt with the text filled with the current selection).