Lidi(리디)

I think it's a bug. According to a document for @commitlint/config-conventional, subject can be either sentence-case or start-case or pascal-case or upper-case. [(link)](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional#subject-case) But linter tell us "subject must not...

@Qix- But an acronym is also upper-case letter. So according to a document for @commitlint/config-conventional, you can write subject with acronym. But it couldn't. It's a bug.

I see. But It seems difficult to decide whether a letter is an acronym or not. Do you have an idea to easily decide whether a letter is an acronym...

Great! But an upper case subject, for example "feat: CORRECT BODY MESSAGE", even if it does not have any an acronym, it is always decided to meet the conventional commits.

Opps! Sorry. I misunderstood! According to a document for @commitlint/config-conventional, when subject is in one of the cases ['sentence-case', 'start-case', 'pascal-case', 'upper-case'], linter always throw an error. So we should...