8000 ci: enforce Conventional Commits with commitlint by norrietaylor · Pull Request #264 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

ci: enforce Conventional Commits with commitlint - #264

Merged
norrietaylor merged 1 commit into
mainfrom
ci/commitlint
May 29, 2026
Merged

norrietaylor merged 1 commit into
mainfrom
ci/commitlint

Conversation

@norrietaylor
Copy link
Copy Markdown
Member

Adds CI enforcement for the Conventional Commits standard introduced in #263.

Changes

  • .github/workflows/commitlint.yml — runs wagoid/commitlint-github-action@v6 on every PR to main, linting all commits in the PR. No Node/npm setup needed; the action bundles commitlint.
  • commitlint.config.js — extends @commitlint/config-conventional, pins the type-enum to the set documented in docs/commit-conventions.md.

Behavior

  • Triggers on pull_request to main with fetch-depth: 0 so the full commit range is available.
  • Fails the check on any non-conforming commit message (bad type, missing colon, empty subject, etc.).
  • permissions: contents: read only.

Notes

  • Depends on docs: adopt Conventional Commits and split CLAUDE.md via @-imports #263 for docs/commit-conventions.md (referenced in a config comment). Merge order is not enforced — the config works standalone.
  • Existing history is not rewritten; enforcement applies to commits in new PRs.
  • If squash-merging, consider linting the PR title instead/additionally — easy to add via the action's title input. Not included here since current merges preserve commits.

🤖 Generated with Claude Code

Add a commitlint job that runs on PRs to main, validating every commit
against @commitlint/config-conventional. Type set matches
docs/commit-conventions.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitai Bot commented May 29, 2026 •
Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@norrietaylor, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 11 minutes and 1 second. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5da110f0-b021-468e-9bed-e0dc4cd78f5c

📥 Commits

Reviewing files that changed from the base of the PR and between 030d011 and 7ed074a.

📒 Files selected for processing (2)
  • .github/workflows/commitlint.yml
  • commitlint.config.js

Comment @coderabbitai help to get the list of available commands and usage tips.

@norrietaylor
Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai
coderabbitai Bot commented May 29, 2026
Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@norrietaylor
norrietaylor merged commit baf967e into main May 29, 2026
8 of 9 checks passed
@norrietaylor
norrietaylor deleted the ci/commitlint branch May 29, 2026 23:05
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.

2 participants

0