Description
Two commit validation mechanisms coexist with slightly different formats:
commitlint (local git hook) — conventional commits format:
<type>(<scope>): <Description.>
Types: feat, fix, docs, style, refactor, test, ci, build, chore, perf, revert, tooling
check-commits.yml (CI) — legacy format:
Pattern: ^[^!]+: [A-Za-z]+.+ .+\.$
Currently both accept the project's existing format (scope: Description.) because commitlint has subject-case: [0] and subject-full-stop: [0] disabled. But the conventional format (feat(scope): Description.) is not validated by the CI regex.
Tasks
Related
Description
Two commit validation mechanisms coexist with slightly different formats:
commitlint (local git hook) — conventional commits format:
Types:
feat,fix,docs,style,refactor,test,ci,build,chore,perf,revert,toolingcheck-commits.yml (CI) — legacy format:
Pattern:
^[^!]+: [A-Za-z]+.+ .+\.$Currently both accept the project's existing format (
scope: Description.) because commitlint hassubject-case: [0]andsubject-full-stop: [0]disabled. But the conventional format (feat(scope): Description.) is not validated by the CI regex.Tasks
check-commits.ymlregex to accept conventional commits formatcheck-commits.ymlwith commitlint in CI (runnpx commitlint --from origin/mainin the workflow)Related