Skip hook assertion on git 1.8 #1325
Merged
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
Hook message is displayed when I run git interactively but does not appear in the console log when the test is run. Not worth the time to research why command line 1.8 is different from all the other git versions that are being tested. Unclear why that old git version behaves differently than all the other versions that are being tested. Not worth the time to investigate the root cause. Accept that command line git 1.8 is a very old version that has several exceptions already included in the plugin.
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.
Skip hook assertions on CLI git 1.8
Hook message is displayed when I run git interactively but does not appear in the console log when the test is run. Not worth the time to research why command line 1.8 is different from all the other git versions that are being tested.
Unclear why that old git version behaves differently than all the other versions that are being tested. Not worth the time to investigate the root cause. Accept that command line git 1.8 is a very old version that has several exceptions already included in the plugin.
Checklist
Types of changes