Husky cannot execute hooks

[Brolly0204]

version

husky: "^1.3.1",
os: Mac
node: v10.7.0

.huskyrc

{
  "hooks": {
    "pre-commit": "npm run lint"
  }
}

[shamatoff]

Same here.

husky: "^1.3.1"
os: Windows 10
node: v10.15.0

There is no custom hooks that prevents Husky.

[danielhdz56]

same here, this is a recurring issue with husky. previous version of husky you could fix this by doing
rm -rf .git/hooks
and then installing husky
npm install -D husky

this doesn't work for me, but maybe it does for y'all.

[tuananh]

@danielhdz56 this does fix it for me. thank you!

[vitalii]

doesn't work for me

[bmesin]

Does not work for me either. Commit and push pass without executing any hooks.

"husky": {
"hooks": {
"pre-commit": "ng lint",
"pre-push": "ng lint && ng build --aot true"
}
},

...

"husky": "^1.3.1",

[vitalii]

check .git/hooks
if it's empty try to uninstall husky and install again. my sh history

 ls .git/hooks
 npm uninstall husky
 npm i husky -D
 ls .git/hooks

it helped me

[SammyIsra]

Yup, deleting .git/hooks directory and reinstalling husky did it for me.

Is there any reason why this runs this way? Is there no command that we can run within husky to check and create the hooks?

Do you also have to do the same thing every time you change your hooks? It seems a bit inconvenient if that's the case.

Maybe we can submit an MR to get around the issue?

[radiocity]

@shamatov, try to uninstall Windows Subsystem for Linux (WSL) by running lxrun /uninstall /full /y. The problem caused by custom bash executable.

[zhixuanziben]

@vitalii It does work for me, Thanks!

[chat-du-cheshire]

Hi, I'm trying to run custom hook from husky. I have package.json file and folder "custom-hooks" where I've my custom pre commit. But config like this

[wataruoguchi]

Hi, I had the same issue. The hooks didn't work. Here's what I did.

Make sure you understand it changes the valid location of hook files. If you're not familiar with this, talk to your peer before you run the commands.

1. Check where your git hooks are: $ git rev-parse --git-path hooks
2. Then if it's not .git/hooks, run git config core.hooksPath .git/hooks/ to solve the problem.

It seems like the hooks files are created in .git/hooks/ no matter what the core.hooksPath is.

[403studio]

first,you shoule check the .git/hooks if there are some hooks,such as pre-commit ,and check its content,if husky is corrected configed,you can see some content
second,if the .git/hook does not has hooks,that means husky isnt take place.you shoule reinstall husky.for me at this moment i find the problem

when i uninstall husky,the terminal show:
Husky requires Git >= 2.13.2, please update Git
so i update my git and reinstall husky, everything is ok

[erikwatson]

I was installing husky via the official node docker image for 10.16. These are based on Debian, which does not have access to a version of Git as high as is required for Husky to work. I've bashed together a new Dockerfile based off of the Ubuntu images instead to get around this.

It's also worth noting that while running npm install does give the "please update git" message, it doesn't appear to show when using Yarn to install your dependencies. This left me scratching my head for a while.

[typicode]

Closing it some fixes have been suggested. Also it's related to a pretty old husky version.

As for Debian, it seems that Debian Buster has now a version of Git without the issue. Even though not ideal for the moment and for people stuck with older versions of Debian, it should hopefully be fixed with time.

Yarn seems to hide console.log messages during install. I don't really know what could be done about that, but I would be scratching my head too.