-
Notifications
You must be signed in to change notification settings - Fork 934
Rule for forcing commit body #875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
No thoughts so far. I don't think someone asked for this so far. @byCedric you remember anything? |
the same as we have scope-empty, subject-empty we need to have |
I find the current behavior very surprising. If the |
Is there any update about this ? I am looking to have the same for the footer too |
to my knowledge there are rules for this already https://github.com/conventional-changelog/commitlint/blob/master/%40commitlint/rules/src/footer-empty.ts it looks like we are missing them in documentation |
You are right I test it and it works. Thanks ! The doc should be update yeah |
Created a PR for the docs. |
Looks good to me thanks |
Hi,
It seems like there is not a rule for forcing a message in the commit body.
I took a look here but only found the
body-min-length
rule.At first I thought I could force adding something to the body by enabling the rule and setting a minimum length of, let's say 5. But it seems like the rule does not apply if the commit body is left completely empty.
Are there any thoughts on implementing a
body-exists
rule?The text was updated successfully, but these errors were encountered: