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
When I try to submit a breaking-change commit with the provided conventional commit config file used, I get an error:
husky > commit-msg (node v10.15.3)
⧗ input: test!: should work
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
husky > commit-msg hook failed (add --no-verify to bypass)
Expected Behavior
This commit should pass the husky check because it falls in the spec of a conventional commit
Current Behavior
The commit fails the lint, probably because the exclamation point isn't getting parsed correctly
Affected packages
cli
core
prompt
config-angular
Possible Solution
Steps to Reproduce (for bugs)
attempt to commit changes with an exclamation point after the type/scope but before the colon
Hi @topocount! I see you are running an outdated version of commitlint (6.4.1), this doesn't have support for the new format of the conventional changelog parsers. We made some internal changes in [email protected] that includes support for these parsers.
If you upgrade to 8.3.3, the exclamation mark should be parsed as breaking change commit (without any failing type/scope/message rules).
When I try to submit a breaking-change commit with the provided conventional commit config file used, I get an error:
Expected Behavior
This commit should pass the husky check because it falls in the spec of a conventional commit
Current Behavior
The commit fails the lint, probably because the exclamation point isn't getting parsed correctly
Affected packages
Possible Solution
Steps to Reproduce (for bugs)
commitlint.config.js
Context
Your Environment
commitlint --version
git --version
node --version
The text was updated successfully, but these errors were encountered: