Execute pre_commit_script as a complete path #305
+3
−12
Conversation
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
Prior to this the pre_commit_script needed to be in contrib, as shipped by the gem. This gives complete freedom on what to run, which gives a lot more freedom.
ekohl
force-pushed
the
make-pre-commit-script-free
branch
from
f1b4a81 to
21ce8fe
Compare
Member
|
@TheMeier any chance you can test this? |
|
I will try to look at it. But can't promise anything ATM |
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.
Prior to this the pre_commit_script needed to be in contrib, as shipped by the gem. This gives complete freedom on what to run, which gives a lot more freedom.
Currently untested, but @TheMeier recently did a work on cleaning up fixture files. This would allow creating a script that does all the clean ups on every modulesync, and more.