Conversation
removed by running following command: yarn remove husky && git config --unset core.hooksPath
|
This is cool! Working great. Should we consider |
Yeah lol was actually thinking the same, the only one point where husky shines is due to its popularity and some people might feel home when using it in SE-2 instead of seeing lefthook but its just small thing and don't think it will cause a lot of difference. Maybe we test the Also cc @Pabl0cks could you please also give it a shot once on windows? To test, you could follow "To test" section of this #35 (comment) |
It's working nicely on Windows! Tried GH Desktop, Git bash and VSCode. Similar outputs: |

Description:
Migrated to lefhook from husky due #49.
The main selling point of lefthook for us:
postinstallto workFixes #48
Notes
LeftHook:
A bit about Git hooks
Git Hooks lets you fire some custom scripts when certain actions happens like (commit, push, etc). All you need is good knowledge of Bash scripts and internals of git. You can configure it in
./.git/hooks/pre-commit.But while working on project you are interested in that project’s code—not the code that checks it. Hence tools like husky, lefthook were born.
Lefthook:
The important selling point is that :
Configuring Lefthook:
Add lefthook as dev dependency in
package.jsonRun
lefthookThe above should create an
lefthook.ymlfileExample :
Checkout this [exmaple](https://github.com/evilmartians/lefthook/blob/master/docs/configuration.md#run) for various commands