2.8.0 doesn't make any commits
See original GitHub issueWith version 2.8.0
I can no longer make any commits, where it usually prints the new commit, it doesn’t print anything at all. No commit is created, no error message is printed, and the exit code is still 0
.
This is on OS X with zsh.
Reverting to 2.7.8 fixes the problem
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:14 (9 by maintainers)
Top Results From Across the Web
WebAPI 2.8.0 build error - .git directory is not found ... - GitHub
I was looking through the documentation here, and it looks like we can make it so it doesn't fail when you don't have...
Read more >You just committed a large file and can't push to GitHub
But oops, GitHub complains that you are trying to commit files larger than 50 Mb and even grinds to a halt if they...
Read more >Sudden failures for the same commit despite no changes in ...
Python 3.3 builds say there's No module named 'typing' (true, but while there's a PyPI package to backport it the list of installed...
Read more >Why does git status show branch is up-to-date when changes ...
git pull does two operations; first it does a git fetch to get up to date with the commits in the remote repo...
Read more >pre-commit
We run our hooks on every commit to automatically point out issues in code such as ... If one of your developers doesn't...
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 FreeTop 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
Top GitHub Comments
@zacharytelschow Those adapters probably need to implement the changes in the Inquirer 1.0 API. You can see these changes here: https://github.com/commitizen/cz-conventional-changelog/commit/807b4e5d
At the end of the day we probably need to have some compatibility checking between adapters and the commitizen cli so that if you try to commit and your adapter isn’t compatible with the cli you’re using then you’re prompted to contact the adapter author.
Since were now on version 4.x can this be closed?