False positives when using the slash symbol (/) in scope · Issue #262 · conventional-changelog/commitlint · GitHub

If you include the slash symbol (/) in the scope of a commit message, subject-empty and type-empty rules start throwing errors. Current Behavior For the commit message feat(components/Component): subject, I am currently getting the follo

commit lint issuePrefixes - scope could not be optional · Issue

Conventional commit messages, code linting with Git hooks

GitHub - conventional-changelog/commitlint: 📓 Lint commit messages

fix: possible false positive of linting commit title · Issue #3520

Respecting the optional scope in Conventional Commits · Issue #179

Unable to mark issue as false positive - SonarCloud - Sonar Community

Reporting] Refused to execute inline script error in Kibana log

husky - Strange error when attempting to commit. [subject-empty

Error when used with Husky: Please add rules to your commitlint

Conventional commit messages, code linting with Git hooks

Apply conventional commit style on your project with commitlint