header-full-stop?

Expected Behavior

To be able to control full stops on my type-less, scope-less commit messages.

Current Behavior

I’m using commitlint with:

type-empty: [2, always]
scope-empty: [2, always]

According to the parser, I have an empty subject and what would usually be the subject, is understood by the parser to be the header. The header does not, at the moment, have a full stop setting. I’d love either header-full-stop or the parser recognising my subject correctly.

Affected packages

• core
• cli
• prompt
• config-angular

Steps to Reproduce (for bugs)

$ echo "Blah, blah, blah, blah, blah, blah." | commitlint

⧗   input: Blah, blah, blah, blah, blah, blah.
✔   found 0 problems, 0 warnings

.commitlintrc.yml

<div class="highlight highlight-source-yaml">

  rules:
      header-max-length: [2, always, 50]
      header-min-length: [2, always, 1]
      body-max-line-length: [2, always, 72]
      body-min-length: [2, never]
      footer-max-line-length: [2, always, 72]
      footer-min-length: [2, never]
      subject-max-length: [2, always, 50]
      subject-min-length: [2, always, 1]
      scope-empty: [2, always]
      type-empty: [2, always]
      signed-off-by: [2, never]
  

</div>

Your Environment

Executable	Version
commitlint --version	7.2.1
git --version	2.20.0
node --version	11.4.0

[byCedric]

This has been released in 7.4.0! 😄 Let me know if it works fine, or if you encounter some issues with the new rules. Good luck!

[shreyasminocha]

Thanks @byCedric!