Commitlint: footer-leading-blank is complaining when there is no footer

[gajus]

When attempting to submit a commit:

chore: force add README.md
This is designed to be used in combination with .gitignore ./README.md when dynamically generating documentation.

I am getting:

⧗ input: chore: force add README.md
✖ footer must have leading blank line [footer-leading-blank]
⚠ tense of body must be present-imperative. Verbs in other tenses: is - present-third-person,generating - present-participle,starting - present-participle,is - present-third-person,commits - present-third-person,staged - > past-tense [body-tense]
⚠ header must not be shorter than 30 characters [header-min-length]
⚠ message must be lowerCase [subject-case]
✖ found 1 problems, 3 warnings

There is no footer, therefore there must be no warning.

[skipjack]

I'm running into this issue as well, the footer isn't a requirement, is it?

If it helps this error isn't thrown if you only have a subject and leave out the body and footer. However, when a body is included without a footer, this error seems to always get thrown.

[marionebl]

This issue is part of the roadmap to version 1 / a planned commitlint renamer. I'll pick it up as soon as possible, stay tuned.

Thanks for the additional detail!

[skipjack]

@marionebl no problem, thanks for the awesome tool! Glad to hear you're actively working on the project.

Side Note: Is there any way to ignore tense for certain patterns (e.g. with a regex or something)? If not, maybe I'll create another ticket with that as a feature request. For example, I have a package name that ends with -fetching and, when i mention in the commit subject, it throws a warning. (Arguably I should maybe rename that package, but I could definitely see this being useful in a variety of cases)

[marionebl]

@skipjack A feature request would be cool