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.

git cz just opens the local editor

See original GitHub issue

git cz is broken for me.

I wanted to get started but it does not work.

I’m using Windows WSL (ubuntu shell on windows) together with zsh.

This is my gitconfig:

[alias]
        l = log --graph --color --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --
        ls = ls-files
        st = status
        amend = commit --amend
        amendn = ammend --no-edit
        diffs = diff --staged
        ch = checkout
        f = fetch
        p = push
        c = commit
        a = add -p
        r = reset -p
        aliases = !git config -l | grep alias | cut -c 7-
        whois = !sh -c 'git log -i -1 --pretty=\"format:%an <%ae>\n\" --author=\"$1\"' -
[diff]
        tool = meld
[push]
        default = simple
[core]
        autocrlf = input
[branch]
        autosetuprebase = always

Even with my gitconfig removed, I get the following:

cz

Is there a known bug?

Issue Analytics

  • State:open
  • Created 5 years ago
  • Reactions:5
  • Comments:24 (9 by maintainers)

github_iconTop GitHub Comments

56reactions
achillesrasquinhacommented, Dec 9, 2018

Faced the same issue. You can enforce this globally as mentioned within the README. Here’s a one-liner fix:

$ npm install -g commitizen cz-conventional-changelog && echo '{ "path": "cz-conventional-changelog" }' > ~/.czrc
17reactions
sfauvartcommented, Oct 1, 2018

Hello, I have the same issue (but on real Linux system 😃) I think it’s the same problem in issue #558 You have to run

commitizen init cz-conventional-changelog --save-dev --save-exact

before to make your repo comittizen friendly

I think the readme should be updated to indicate the command to be executed for new projects as a commitizen beginner, it did not seem very clear to me 😉

Read more comments on GitHub >

github_iconTop Results From Across the Web

How can I fix git commit error "Waiting for your editor to close ...
Opening a Terminal in Visual Studio Code and hitting git config --global core.editor "code --wait" solved the problem.
Read more >
Commitizen - GitHub Pages
Using the command line tool​​ Simply use git cz or just cz instead of git commit when committing. You can also use git-cz...
Read more >
8. Commiting the changes - GitHowTo
I have the EDITOR variable set to emacsclient (available for Linux and Mac). Let us commit now and check the status. Run: git...
Read more >
Set up ESLint, Prettier, Commitizen, Husky and friends in 2022
It isn't just restricted to javascript, but can also be used to format HTML, CSS, SCSS, ... Husky is a great tool for...
Read more >
PyCharm: the Python IDE for Professional Developers by ...
The Python & Django IDE with intelligent code completion, on-the-fly error checking, quick-fixes, and much more...
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