subject-case has all value but failed when check

Expected Behavior

Current Behavior

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

Steps to Reproduce (for bugs)

1. commit with different message had different behaviour
2. git commit -m “chore: update config to support publicPath” -> failed
3. git commit -m “chore: update config to support publicpath” -> success
4. git commit -m “chore: 更新配置支持 publicPath” -> success

commitlint.config.js

module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    'scope-case': [
      2,
      'always',
      [
        'lower-case',
        'upper-case',
        'camel-case',
        'kebab-case',
        'pascal-case',
        'sentence-case',
        'snake-case',
        'start-case',
      ],
    ],
    'subject-case': [
      2,
      'always',
      [
        'lower-case',
        'upper-case',
        'camel-case',
        'kebab-case',
        'pascal-case',
        'sentence-case',
        'snake-case',
        'start-case',
      ],
    ],
  },
}

Context

there are all configs, so i think i could type any kind of message, but as mentioned before, some kind of message failed. i want to know is it a bug or my config is wrong

Your Environment

Executable	Version
commitlint --version	11.0.0
git --version	2.30.1
node --version	14.15.1

[keeplz]

Thanks @curly210102 !

@540692039 if you want to figure it out, have a look youself. Happy for any feedback or a PR to improve this. In general I think this is not a real usecase and wouldn’t bother to “fix” this and would close this issue.

ok thanks all of you

[curly210102]

@540692039 You can get possible values of ‘subject-case’ by Official document, And learn the machanism by https://github.com/conventional-changelog/commitlint/blob/master/%40commitlint/rules/src/subject-case.ts.