husky > pre-commit hook failed (add --no-verify to bypass)

Question

Suddenly I am getting the "husky > pre-commit hook failed (add --no-verify to bypass)" error message when I give the git commit.

(C:\Windows\System32\cmd.exe)
> git commit
husky > npm run -s precommit (node v12.18.3)

'pretty-quick' is not recognized as an internal or external command,
operable program or batch file.

husky > pre-commit hook failed (add --no-verify to bypass)

I tried git clean command too. Anyone faced similar issue?

You can also delete the .git/hook folder and then uninstall and reinstall husky. There are some conflicts with husky generated files and .git/hook/ files. That worked for me — Elio, Apr 12 '21 at 10:47

Sathiamoorthy · Accepted Answer · 2023-05-03T13:58:21.150

175

Husky can prevent you from bad git commit, git push and more. If you are getting this error check your code syntax. In case you are getting this error even if your code is valid, please use the below solution.

#Solution 1:

Delete the .git/hooks folder and then do the npm install for reinstall husky. There are chances for conflicts with husky-generated files in the .git/hooks/ files.

#Solution 2:

this is a temporary/quick solution.

git commit -m "message" --no-verify

edited May 03 '23 at 13:58

answered Sep 18 '20 at 03:25

Sathiamoorthy

8,831
9
65
77

1

It's helped me while no need to check any code syntax and other lints. Thank you @Sathia – Vikas Ukani Mar 08 '21 at 15:19
4

delete the .git/hook folder in project directory and tried code committing it again and it worked for me like a charm. Thanks !! – Sagar B Jul 02 '21 at 18:41
2

Deleted .git/hooks folder and committed again. This worked for me as well – Gihanmu Aug 27 '21 at 07:30
3

It's `hooks` plural. Deleting it worked for me. Thanks! – Ian Aug 30 '21 at 22:14
2

delete the .git/hooks worked for me as well! – Don D Oct 04 '21 at 05:13
why would I want to add --no-verify everytime – Philip Rego Oct 09 '21 at 02:23
1

deleting .git/hooks worked for me too! – Semaphor Nov 18 '21 at 15:24
You don't even have to reinstall husky. I had to remove .git/hooks and was able to commit – nnn Jan 20 '22 at 15:25
1

Because I changed from using npm to yarn, thus has this issue, but fixed with this": Delete the .git/hook folder and then do the npm install for reinstall husky. There are chances for conflicts with husky-generated files and .git/hook/ files. – Frank Guo Mar 09 '22 at 12:04
1

Wonderful solutions, first solutions worked, 2nd not needed to try for me! Thanks – Md. Abu Sayed Apr 18 '22 at 19:13
In case someone stumbles to this place looking for help on php-husky, it was failing for me because `.git` direcotory didn't exist. – Pratik Patel Sep 08 '22 at 16:49
git config --unset core.hooksPath – Nikasha Von carstein Apr 21 '23 at 13:34
how/where to find this folder "git/hook"? – Sachin Mankotia Jul 21 '23 at 04:20
The first solution didn't work for me. As for the second, is there already some way to not write all the time --no-verify? It works but it stresses me out – HackerMF Aug 30 '23 at 15:18

score 7 · Answer 2 · edited Jan 19 '22 at 00:52

The Comment by @Elio is a much preferred solution, as --no-verify is skipping whatever scripts that should run.

I assume here that if the scripts are there it is for a reason...

Therefore:

You can also delete the .git/hook folder and then uninstall and reinstall husky. There are some conflicts with husky generated files and .git/hook/ files. That worked for me

In my case, the uninstall/re-install was not necessary.

Zerzavot · Answer 3 · 2022-01-06T17:45:09.980

6

I find two temporary solution like that

git config --unset core.hooksPath

or

git commit -m "message" --no-verify

edited Jan 06 '22 at 17:45

answered Dec 30 '21 at 08:36

Zerzavot

135
1
3

The first command worked for me, but what does it do exactly? – Ralph David Abernathy Jun 28 '22 at 17:17

score 4 · Answer 4 · answered Sep 16 '21 at 06:45

I'm surprised that the top answer suggests just to omit hooks' verification. If you have Husky hooks, you cannot just ignore them.

In my case I started getting husky > pre-commit hook failed (add --no-verify to bypass) once some dependencies have been updated. The problem was solved by changing Husky's pre-commit linting command to npm run lint (usually this one works fine in most cases) in husky file:

// .huskyrc.json
{
  "hooks": {
      "pre-commit": "npm run lint"
  }
}

Note: the solution works if lint script is declared in your package.json; in my case I have:

// package.json
{
  "scripts": {
    "lint": "tsc && eslint \"src/**/*.{js,ts,tsx}\" --quiet --fix"
  }
}

score 2 · Answer 5 · answered Jun 08 '22 at 05:43

2

For me I had to add

"lint-staged": {
  "**/*": "prettier --write --ignore-unknown"
},

to my package.json

answered Jun 08 '22 at 05:43

pfcodes

1,055
2
9
15

You forgot to add that lint-staged is a separate npm package – Ivan Frolov Mar 02 '23 at 13:51

score 1 · Answer 6 · answered Jan 13 '22 at 03:18

1

I came with the same annoying error message when commit to a electron.js project. Adding --no-verify option works, but it's also a bit annoying that I have to do it everytime when commit.

Then I found the something related to precommit in package.json file:

{
  "scripts": {
    ...
    "precommit": "lint-staged",
    ...
  }
}

Just remove the above line solved my problem.

answered Jan 13 '22 at 03:18

gchfeng

28
4

1

i suppose it switch off husky hook, similar to remove hooks from .git folder. this way just bypass the problem but not solving it – Artem Vertiy May 05 '22 at 20:16
@ArtemVertiy Husky no longer supports precommit hooks in package.json, hooks are defined in .husky folder – Spock Mar 05 '23 at 17:03

score 0 · Answer 7 · answered Aug 28 '23 at 11:27

0

This solution worked for me on NestJS application. Use prettier version 2 instead of version 3.

My solution:

npm i -D  prettier@2.8.8

answered Aug 28 '23 at 11:27

Amir

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Aug 29 '23 at 08:00

score 0 · Answer 8 · answered Aug 30 '23 at 15:29

0

One of the reasons why it happens is because your pre-commit file contains npm test and if you don't have any tests then you will get this error. The way to fix it is either to add tests or remove npm test from pre-commit file

answered Aug 30 '23 at 15:29

HackerMF

475
7
18

husky > pre-commit hook failed (add --no-verify to bypass)

8 Answers8

#Solution 1:

#Solution 2:

Linked