Update install.sh with optional hook_name parameter, and use latest #249
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
added 7 commits
September 8, 2020 18:32
…h talisman into .git/hooks/bin
svishwanath-tw
approved these changes
Sep 8, 2020
|
@dcRUSTy : It looks like he's talking about the script to install talisman for a single repo. Not the one that installs talisman as a global hook. |
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.
Changes to install.sh:
hook_nameparameter so that the user can select whether they want a pre-commit or pre-push hook for their single repository installVERSIONto "v1.8.0"SHAstalisman_hook_script.bashalong withtalismanbinary into.git/hooks/bin.git/hook/$HOOK_NAMEis now just a one-liner that setsTALISMAN_BINARY=".git/hooks/bin/talisman"and calls.git/hooks/bin/talisman_hook_script.bashAlso includes docco update.