question-mark
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.

Error after update to 3.4.1 : Command failed with exit code 1: git config --get core.hooksPath

See original GitHub issue

Hello @carloscuesta!

Issue: I have just updated the gitmoji-cli from version 3.4.0 to 3.4.1, and now I have an error message when I do a commit with the command gitmoji -c. The commit is well created, and I can push it to my repository, so I’m not blocked but the error appears each time I do a commit with gitmoji-cli. I have updated the tool with the command: npm i -g gitmoji-cli

OS: macOS Big Sur 11.2.3 gitmoji -v: 3.4.1 Node version: node: v15.14.0 / npm: 7.10.0 git version: git version 2.24.3 (Apple Git-128)

Error Message:

Error: Command failed with exit code 1: git config --get core.hooksPath
    at makeError (/usr/local/lib/node_modules/gitmoji-cli/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/usr/local/lib/node_modules/gitmoji-cli/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at async getAbsoluteHooksPath (/usr/local/lib/node_modules/gitmoji-cli/lib/utils/getAbsoluteHooksPath.js:17:7)
    at async isHookCreated (/usr/local/lib/node_modules/gitmoji-cli/lib/utils/isHookCreated.js:18:22)
    at async withClient (/usr/local/lib/node_modules/gitmoji-cli/lib/commands/commit/withClient/index.js:26:9) {
  shortMessage: 'Command failed with exit code 1: git config --get core.hooksPath',
  command: 'git config --get core.hooksPath',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: '',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

Screenshot:

error

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:11 (8 by maintainers)

github_iconTop GitHub Comments

4reactions
carloscuestacommented, Apr 26, 2021

Working on a fix!

2reactions
carloscuestacommented, Apr 26, 2021

Hey @wijourdil thanks for opening an issue, this is related with #578 will try to take a look today!

Hey @flo-sch could you take a look at this too?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Git hooks : applying `git config core.hooksPath` - Stack Overflow
the old pre-commit script still runs on commit if I leave it in my-repo/.git/hooks; running git config --get core.hooksPath in my-repo outputs ....
Read more >
githooks Documentation - Git
Just before starting to update refs on the remote repository, the pre-receive hook is invoked. Its exit status determines the success or failure...
Read more >
Setting a global hooks path causes "Cowardly refusing to ...
I recently setup a global spell checking commit hook that lives in git config --global core.hooksPath ~/dotfiles/gitHooks Just noticed that ...
Read more >
Store your git hooks in a repository and setup them for all the ...
Create your global .gitconfig file in the repo. Execute this command: git config -f .gitconfig core.hooksPath hooks. 3. Commit your new ...
Read more >
Bug List - Bugs - Eclipse
ID▽ Product Comp Assignee Status Changed 581252 JGit JGit jgit.core‑inbox NEW Tue 15:20 581243 JGit JGit jgit.core‑inbox NEW Sun 23:23 581234 JGit JGit jgit.core‑inbox NEW 2022‑12‑16...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found