Closed cengels closed 8 months ago
Thanks for your report, I'll check it soon 🙏
@KeisukeYamashita I tested this in 0.1.8 and the original problem doesn't appear anymore, but now it seems the description-empty
rule can't be triggered anymore at all? If I type echo "" | commitlint
with description-empty.level: error
, the validation passes without errors.
@cengels Opps, it might be a bug, let me check it later! Thank you for your report!!!
Describe the bug
Sorry for the many bug reports, but I hope this will help make
commitlint-rs
better!git commit -m "s"
If a type is supplied (like
git commit -m "chore: s"
), all 3 errors go away.Config
Error message
N/A
Expected behavior
Only the message
type is empty
should be printed here, as there is a non-empty description and it is not longer than thedescription-max-length
.Version
Additional context
N/A