Should commitizen be opt-in?

[joematthews]

I think commitizen is great for individuals and teams that want to acquaint themselves with convention commits.

In exteme-angular you can omit the message of a commit (git commit) and commitizen will prompt with a interactive CUI guiding you thru how to create a conventional commit.

However, when committed with a well formed convention commit message, The user can use CTRL-C to skip commitizen and use the commit message (but this is not communicated in the prompt at all. Also commitizen does not report the commit message after completing the prompts.

I do see value in commitizen, but should should it be disabled by default, or removed, in favor of clarity and then rely solely on commitlint to report missing convention commit message components?

[replete]

Just to chip in on this, it's very nice but is yet another dependency I might avoid in a big org and rather enforce good commits in PR review processes. I did like the experience of the popup in github desktop when I tried to commit something with a capital letter in it, but its yet another piece of software in the stack - but again this might be vital in some orgs. Maybe non default is better?

[joematthews]

Thank you for the feedback on this! I think I will keep commitlint for now, but commitizen has never really sat well with me and will likely be removed from the next release. Closing this issue out.