ci: add a commitlint workflow reporting Lint commit messages - #38
Merged
radiusred-cody[bot] merged 1 commit intoSep 3, 2026
Merged
Conversation
The org ruleset require-lint requires a status check with the context "Lint commit messages" on every public repo's default branch, and this repo had no workflow that runs on pull_request, so no PR here could report it and task finish refused NO_CHECKS. Add a single-job workflow whose job is named exactly "Lint commit messages", running wagoid/commitlint-github-action against the PR's commits, with a root commitlint.config.mjs extending config-conventional. The action bundles commitlint, so no package manifest or lock file is needed.
![radiusred-checky[bot]](https://avatars.githubusercontent.com/in/4719924?s=60&v=4){kind=small}
There was a problem hiding this comment.
Approved.
Evidence checked independently:
- The checks API for head d92386a reports one successful check-run named exactly
Lint commit messages; the main-branch organization rules require exactly that context (ruleset 17497708). - The two-file diff matches the recorded #37 plan and the operator-amended M1-R2 scope. It does not touch either reusable release workflow or
.github/actions/calculate_version/. - The workflow and config match the cited
radiusred/codecrew-wwwmodel. The action defaults to the rootcommitlint.config.mjs, bundles@commitlint/config-conventional, and the conventional commit on this PR passed. contents: readis minimal and sufficient as demonstrated by the successful run. The@v6major-version pin is consistent with the explicitly recorded project decision and existing org model.- PR #36 changes a disjoint file set, and a merge-tree of the two PR heads completed cleanly.
- The PR description and #37 record accurately describe the implementation, verification, scope, and lack of deviations.
The diff documents no shell commands to execute verbatim.
radiusred-cody
Bot
deleted the
task/37-add-a-commitlint-workflow-so-prs-in-gith
branch
September 3, 2026 08:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #37
What was done
Two files, nothing else:
.github/workflows/commitlint.yml— runs onpull_requestwithcontents: read; one jobcommitlintwhosename:is exactly Lint commit messages, checking out with full history and runningwagoid/commitlint-github-action@v6over the PR's commits.commitlint.config.mjsat the repo root —extends: ['@commitlint/config-conventional'], the action's default config path.Untouched:
reusable-release.yml,reusable-finalize-release.yml,.github/actions/calculate_version/. No files overlap with #36.Requirements
Why this shape
The org ruleset
require-lintrequires the status-check contextLint commit messagesexactly. ha-sinkhole's workflow (the model named in the task) has no jobname:, so its check reports ascommitlintand would not satisfy the ruleset; codecrew-www's job is namedLint commit messagesand its PRs pass. Decision recorded on the task issue: #37 (comment)Verification
The workflow file rides in this PR's head, so the check ran on this PR itself. Observed via the checks API on commit
d92386a:Lint commit messages— exactly the context the org rulesetrequire-lintrequirescompleted, conclusionsuccess, 21s — run: https://github.com/radiusred/.github/actions/runs/33731210445/job/100571336981The PR's single commit is conventional (
ci: … (#37)), so a pass is the expected outcome; a non-conventional message would fail the same job. YAML was also validated locally before commit. Once this lands, #36 is rebased onto main so the check reports there too (per the task text).Deviations
None from the plan.