Error message is not intuitive
Jason0214 opened this issue · 1 comments
Jason0214 commented
I'm submitting a
- Bug report
- Feature request
- Performance issue
- Regression (a behavior that used to work and stopped working in a new release)
- Documentation issue or request
- Other... Please describe:
Current behavior
I need to look the index.js
to find out the legal format of commit message
Expected behavior
maybe try to add it into commitlint error msg?
the current error message, which is not intuitive, it is better to give some information about what the correct pattern of a commit message look like.
husky > commit-msg (node v9.6.1)
⧗ input:
asdfa
✖ message may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
husky > commit-msg hook failed (add --no-verify to bypass)
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
Jason0214 commented
seems a problem of commitlint