Commit hook is not working anymore since 3.2.9 upgrade
See original GitHub issueHello @carloscuesta!
Issue:
whenever I git commit
I get this error message: A commit message is already set, cancelling gitmoji
I was using Gitmoji through the git commit hook, setup with gitmoji -i and everything was working fine but it stoped working after upgrading to 3.2.9
OS: macOS 10.15.6 (19G2021) gitmoji -v: 3.2.9 installed via brew Node version: 14.8.0 Git version: 2.28.0
Error Message: A commit message is already set, cancelling gitmoji
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
javascript - lint-staged not running on precommit
Sometimes hooks are not added by husky so you need to add it using a simple easy hack. You need to uninstall husky...
Read more >Hooks not working · Issue #326 · typicode/husky
I have set up husky commit hooks to run on commit and push, it works for me and another dev, but for one...
Read more >Git Hooks
After the entire commit process is completed, the post-commit hook runs. It doesn't take any parameters, but you can easily get the last...
Read more >How to run ESLint using a pre-commit hook - Level Up Coding
Update : There is a better way to add pre-commit hooks to your project. ... add pre-commit hooks but please do note that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @carloscuesta Sorry for the inconvenience, I will look into it. Might need to drop the current way of detecting no interactive (based on presence of git message) and instead use
git status
or some less clever way of detecting that the hook shouldn’t be launched.Yes I reproduced the error, I’m going to revert #415 and release a new version until we found a fix for that