Skip to content

ci: update commit-check-action to v2.13.1, pinned by digest - #54

Merged
shenxianpeng merged 1 commit into
mainfrom
claude/bump-commit-check-action-602anc
Aug 8, 2026
Merged

ci: update commit-check-action to v2.13.1, pinned by digest#54
shenxianpeng merged 1 commit into
mainfrom
claude/bump-commit-check-action-602anc

Conversation

@shenxianpeng

@shenxianpeng shenxianpeng commented Aug 8, 2026

Copy link
Copy Markdown
Member

One line: @v2.11.1@562a184b2b8e583e757b17eb385bc48370f44547 # v2.13.1.

v2.13.1 is the current release (2026-08-07), and the digest is the one the tag resolves to — checked against the tag ref rather than copied.

Why it was worth doing

v2.11.1 predates stable rule IDs, so this repo's own PR checks report failures in the old format — no CC0xx ID, no docs link, and a bare # Commit-Check ✔️ comment with no table or per-scope breakdown.

#53 ran into it live. A commit message leading with cut was rejected, and the advice offered was:

Suggest: Change the first verb to imperative form, e.g., 'fix' instead of 'fixed'/'fixes'/'fixing'

cut is the imperative. The rule was reporting a past tense that was never written, because the verb simply was not on the list — which is the whole of commit-check#526.

Pinned by digest

actions/checkout two lines above is already digest-pinned with the version in a comment, and so is the commit-check workflow in commit-check itself. This line was the odd one out; now it matches. Tag pins are movable, which is the thing digest pinning exists to prevent.

What this does not fix

The engine is still commit-check==2.13.4, so the imperative-mood rewrite from commit-check#540 is not in this bump — the action's version does not track the engine's. It arrives here once 2.14.0 ships and the action picks it up. Until then a subject led by an unlisted verb can still be rejected in this repo; it will just be reported more legibly.

Noted, not changed

The trigger includes edited, which fires on description edits, not only title edits — so every bot summary edit costs a full run. A gate like if: github.event.action != 'edited' || github.event.changes.title != null would cut that, but it changes when checks run, so I left it to you.

🤖 Generated with Claude Code

https://claude.ai/code/session_01U9zFxq8V4qxG4aMzJhGBFn


Generated by Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the commit validation workflow to a newer version for improved reliability and security.

v2.11.1 predates stable rule IDs, so failures here report
'Type subject_imperative' with no ID, no docs link, and the old bare
comment header. #53 hit that live: a commit message leading with 'cut'
was rejected, and the advice offered was to stop using a past tense it
had not used.

Pinned by digest with the version in a comment, matching actions/checkout
two lines above and the workflow in commit-check itself.

Engine still 2.13.4, so the imperative fix from commit-check#540 arrives
here when 2.14.0 ships and the action picks it up.
@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 282536ed-2ee1-43ad-9feb-3b5000e70246

📥 Commits

Reviewing files that changed from the base of the PR and between 17eb3d0 and 8b8753a.

📒 Files selected for processing (1)
  • .github/workflows/commit-check.yml

📝 Walkthrough

Walkthrough

The commit-check workflow now uses commit-check v2.13.1, pinned to commit 562a184b2b8e583e757b17eb385bc48370f44547.

Changes

Commit-check workflow update

Layer / File(s) Summary
Update workflow action pin
.github/workflows/commit-check.yml
The workflow changes the commit-check action from v2.11.1 to the pinned v2.13.1 commit.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the workflow update to commit-check-action and the digest pinning.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/bump-commit-check-action-602anc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

Commit Check

All 3 checks passed

Show all 3 checks
Commit message
  ✔ PR title (ci: update commit-check-action to v2.13.1, pinned by digest)
  ✔ Commit 1/1 (ci: update commit-check-action to v2.13.1, pinned by digest)
Branch
  ✔ Branch (claude/bump-commit-check-action-602anc)

commit-check 2.13.4 · Rules reference

@shenxianpeng
shenxianpeng merged commit 8104e2a into main Aug 8, 2026
3 checks passed
@shenxianpeng
shenxianpeng deleted the claude/bump-commit-check-action-602anc branch August 8, 2026 22:37
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