"subject-empty" is over-flagged

[nedbat]

Expected Behavior

Lint a comment message like "try out commitlint." Two errors are flagged:

Error: You have commit messages with errors

⧗   input: try out commitlint.
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

The "subject-empty" error seems silly: the commit message has a subject, it's "try out commitlint." In my opinion, "subject-empty" should only be raised for messages like "fix:", with a type and nothing else.

Affected packages

• cli
• core
• prompt
• config-angular

[escapedcat]

What's you configuration?
The main point of commitlint is to lint according to: https://www.conventionalcommits.org
Also see: https://github.com/conventional-changelog/commitlint#what-is-commitlint

[nedbat]

This happens with the default configuration:

module.exports = {
  extends: ['@commitlint/config-conventional'],
};

I understand the goal of the tool. My point is that it seems nonsensical to say "subject may not be empty". The commit's subject isn't empty, it's "Try out commitlint." The problem is that it doesn't have a type, which is correctly reported as an error.

[gyurielf]

After upgrading to 13.2.x, I experience pretty same.
Just with ruleset, my config is same. I tried to add some rules to the config.
(Sidenote I had to use as cjs, but it works befor the update)

Creating ui-kit_node_run ... done
⧗   input: chore: update packages part two
✖   Please add rules to your `commitlint.config.js`
    - Getting started guide: https://git.io/fhHij
    - Example config: https://git.io/fhHip [empty-rules]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

[tday]

This also causes issues when trying to disable the type-empty rule. subject-empty will fail if the : delimiter is not provided.

[osequi]

See also #3045

[sammcj]

FYI This is still occuring

[ShreddedShekhar]

try giving type in commit as -> git commit -m 'feat: hello world'

type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]