adding GIT_FILTER_VERSION to GIT_FILTER_INIT as part of convention#4267
Merged
Conversation
Member
|
Yep, this probably makes sense and this changes looks good. 👍 One thing we also do is provide a function that will Would you be so kind as to also add a See Thanks! |
Contributor
Author
|
No problem @ethomson ! Just check if all the changes are consistent with what you had in mind 😊 |
Member
|
Awesome, thanks @mohseenrm ! |
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
2 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.
Adding GIT_FILTER_VERSION to GIT_FILTER_INIT.
Stumbled on this while using custom filters via. filter struct.
Also on the recommendation of @implausible.
Similar convention seen in files:
include/git2/sys/blame.h (Line 82)
include/git2/sys/checkout.h (Line 298)
include/git2/sys/cherrypick.h (Line 37)
...