Make the changes between two commits more explicit #92
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
jackton1
requested changes
Jun 9, 2021
jackton1
approved these changes
Jun 9, 2021
|
Thanks @monoxgas |
|
@all-contributors please add @monoxgas for code |
|
@all-contributors please add @monoxgas for code |
|
I've put up a pull request to add @monoxgas! 🎉 |
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.
The current strategy for
git diffcan fail to be accurate in cases where local files are modified as part of the checkout. A common case is changes made to line endings.I've made a small change to track an explicit
PREV_SHAagainst aCURR_SHA(HEADby default). This will ensure file changes accurately reflect only those changes that actually occurred as part of the commit history.