Skip to content

chore(NO-TASK): Use shared linchpin commitlint config - #58

Open
aaronware wants to merge 1 commit into
mainfrom
chore/NO-TASK/shared-commitlint-config
Open

chore(NO-TASK): Use shared linchpin commitlint config#58
aaronware wants to merge 1 commit into
mainfrom
chore/NO-TASK/shared-commitlint-config

Conversation

@aaronware

Copy link
Copy Markdown
Contributor

Replaces this repo's inlined commitlint rules with @linchpinagency/commitlint-config, so the convention ships from one place instead of drifting per repo.

Part of an org-wide rollout. A survey of all 175 linchpin repos found 72 that lint commits, across 30 distinct config variants — the drift this consolidates.

Behaviour is unchanged

This repo verified as a zero-regression swap. Every commit in its recent history was replayed through both the old config and the shared one:

  • Identical pass/fail result under each
  • Zero commits that pass the old config and fail the new one

The shared config was deliberately widened first (commitlint-config#4) to accept add and remove, so it is a superset of this repo's rules rather than a tightening.

What to check

The commit-msg hook picks the rules up from the package after the next npm install.

Task: NO-TASK

🤖 Generated with Claude Code

Replaces the inlined rules with @linchpinagency/commitlint-config so a
convention change ships from one place instead of drifting per repo.

Behaviour is unchanged. Replaying this repo's recent commit history
through the old and new configs gives an identical pass/fail result, with
zero commits that pass the old config and fail the new one.
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