Skip to content

fix(ci): disable body-max-line-length in commitlint config#84

Merged
samuelds merged 1 commit into
developfrom
fix/commitlint-body-max-line-length
Apr 29, 2026
Merged

fix(ci): disable body-max-line-length in commitlint config#84
samuelds merged 1 commit into
developfrom
fix/commitlint-body-max-line-length

Conversation

@samuelds
Copy link
Copy Markdown
Contributor

Problème

Le check commitlint de la PR #83 (release/cli-1.9.0-to-mainmain) échoue car la CI scanne les commits depuis base.sha (tip de main = 900fe4e6) jusqu'au HEAD de la branche release — soit 53 commits historiques.

Le commit 7bc498a (fix(catalog): default URL targets GitHub Pages CDN + bump 1.3.0) a un body d'une seule ligne de ~120 chars, ce qui dépasse la limite body-max-line-length: 100 héritée de @commitlint/config-conventional.

Solution

Désactiver body-max-line-length avec [0] (severity 0 = off). Les corps de squash-merge embarquent des descriptions de PR qui peuvent légitimement dépasser 100 chars. La contrainte utile reste header-max-length: 100 sur le titre.

Test

pnpm exec commitlint --config config/commitlint.config.js --from 900fe4e6 --to origin/release/cli-1.9.0-to-main --verbose
# → aucun problème détecté

Fixes #83 (commitlint check).

🤖 Generated with Claude Code

Squash-merge commits embed PR descriptions that can contain lines
longer than 100 chars. The rule inherited from @commitlint/config-conventional
caused spurious CI failures when scanning historical commits on
release branches. Disabling the rule with severity 0 to fix PR 83.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@samuelds samuelds force-pushed the fix/commitlint-body-max-line-length branch from df3bd90 to e93bdff Compare April 29, 2026 09:11
@samuelds samuelds merged commit f5f5cea into develop Apr 29, 2026
10 checks passed
@samuelds samuelds deleted the fix/commitlint-body-max-line-length branch April 30, 2026 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant