You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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?
The text was updated successfully, but these errors were encountered:
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 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?
The text was updated successfully, but these errors were encountered: