support -m

[srghma]

Expected behavior:

git cz -m "somemessage"

expected: results in prefilled somemessage

actual: results in prefilled Write a short, imperative tense description of the change:

[pawamoy]

Yes, too disruptive for me right now. I'm used to always type gc -am "my commit message". I would like to be able to do the same with gz -am "my commit message", then choose the type and scope of the commit. The short message and long description would be prefilled with the given string.

[jedwards1211]

Same goes for adding the prepare-commit-msg hook, I added the recommended one and it pops up the "Select the type of change that you're committing:" menu even if I use -m.

yeah I really only want to use commitizen as an aid for other contributors, I'm used to the message format so it's faster for me to type it out manually.

[jedwards1211]

okay finally figured out a work around for husky hooks:

"prepare-commit-msg": "grep -qE '^[^#]' .git/COMMIT_EDITMSG || (exec < /dev/tty && git cz --hook || true)",

I guess this wouldn't behave as expected if you do something silly like -m " " but good enough