You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
If included in the type/scope prefix, breaking changes MUST be indicated by a ! immediately before the :. If ! is used, BREAKING CHANGE: MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.
But gitlint reports error if adding ! after the scope:
$ echo'test(scope)!: title'| gitlint --contrib=CT1 -c general.ignore=body-is-missing
1: CT1 Title does not follow ConventionalCommits.org format 'type(optional-scope): description': "test(scope)!: title"
The text was updated successfully, but these errors were encountered:
linjiX
changed the title
Contrib rule CT1: contrib-title-conventional-commits do not support the BREAKING CHANGE symbol "!"
CT1: contrib-title-conventional-commits do not support the BREAKING CHANGE symbol "!"
Apr 3, 2021
- Python 3.10 support
- New Rule: ignore-by-author-name allows users to skip linting commit messages
made by specific authors
- --commit <SHA> flag to more easily lint a single commit message (#141)
- --fail-without-commits flag will force gitlint to fail (exit code 253) when
the target commit range is empty (typically when using --commits) (#193)
- Bugfixes:
- contrib-title-conventional-commits (CT1) now properly enforces the commit
type (#185)
- contrib-title-conventional-commits (CT1) now supports the BREAKING CHANGE
symbol "!" (#186)
- Under-the-hood: dependencies updated, test and github action improvements.
Full Release details in CHANGELOG.md.
According to the Conventional Commits
But gitlint reports error if adding
!
after the scope:The text was updated successfully, but these errors were encountered: