Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Commit does not work if there are git hooks from husky and lint-staged

See original GitHub issue

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.58.2

code --version    
1.58.2
c3f126316369cd610563c75b1b1725e0679adfb3
x64

OS Version: Ubuntu 20.04

Steps to Reproduce:

configure husky and lint-staged
check that commiting from CLI works
try commiting from VSCode
get error “Git: Failed to execute git”
see following in git log in Output:

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
> git config --get-all user.name
> git config --get-all user.email

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:8

Top GitHub Comments

2reactions

alexamycommented, Feb 20, 2022

Having the same problem, but with yarn: command not found, my temp solution was to edit ~/.huskyrc, as mentioned here:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"

1reaction

rmclaughlin-nelnetcommented, Aug 26, 2022

I am having the same problem. When I view the git logs I see this. This only recently started happening to me so it may not be the same as mentioned in the op

[2022-08-26T17:50:51.747Z] env: node: No such file or directory
husky - pre-commit hook exited with code 127 (error)
husky - command not found in PATH=/usr/local/Cellar/git/2.35.1/libexec/git-core:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin