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.
Hello, great project @toplenboren! Just migrated from Husky myself and have to say this project works in a much more elegant fashion DX-wise.
Inspired by #34 I've added built-in support for auto-updating the hooks on commit. It's tested this with both npm and Yarn. In addition, it should not break anything for people who already added the update script to the
pre-commithook, but in these cases it will run thesimple-git-hookscommand twice.This all works by running a
simple-git-hookscommand instead of the user-specifiedpre-commitcommand. This command uses both asilentoption so the user's terminal isn't bloated with messages when updating the hooks, and anautooption which executes the configuredpre-commit.Would love to hear what you think!
Edit: It should probably be mentioned in the release notes/upgrade guide that you need to run the
simple-git-hooksonce with the new version before the automation kicks in.