You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d216058
Browse filesBrowse the repository at this point in the historyBrowse files
fix(install): start each invocation from an empty work dir, wheels only; doc fixes
- action.yml removes $RUNNER_TEMP/commit-check-action before use, so a
second invocation in one job cannot leave two commit_check wheels for
the attestation glob; pip download takes --only-binary=:all: so a
platform without wheels fails at download time with pip's message
instead of at the offline install.
- README comparison table: the Action's title and author checks are
opt-in; the GitHub App reports one check run per commit and posts no
comment.
- Workflow A, docs and README write report.md with printf '%s' so the
posted comment is byte-identical to the report output.
- Workflow B tolerates a missing artifact (A's install failed) with a
notice instead of a red run.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018xYa7m3qup5wyN5MaXFgf6
| **Where it runs** | In your workflow, on the runner, after the push | On the contributor's machine, at `git commit` / `git push` | Hosted by commit-check; installed on the repository, no workflow file |
109
-
| **What it checks** | Every PR commit, the PR title, branch and author; renders a job summary, annotations, a PR comment and the `result` / `report` outputs | Message (`commit-msg` stage), branch, author; tag, force-push and files (`pre-push`) — one commit at a time, before it exists | The pull request's commits, title and branch, reported on the pull request |
110
-
| **When to pick it** | You want enforcement in CI that a contributor cannot skip, per-rule outputs for later steps, or you run on GitHub Enterprise Server / need `CCHK_*` overrides | You want the fastest feedback and to stop bad commits before they are pushed; pair it with the Action, since hooks are opt-in | You want zero YAML and no Actions minutes; fork PRs get comments without the [two-workflow pattern](docs/fork-pr-comments.md) |
109
+
| **What it checks** | Every PR commit's message, plus the PR title, branch and author checks you enable; renders a job summary, annotations, a PR comment and the `result` / `report` outputs | Message (`commit-msg` stage), branch, author; tag, force-push and files (`pre-push`) — one commit at a time, before it exists | Every commit of a push or pull request: message, branch, author (the PR title only in squash mode); reported as one **Commit Check** check run per commit |
110
+
| **When to pick it** | You want enforcement in CI that a contributor cannot skip, per-rule outputs for later steps, or you run on GitHub Enterprise Server / need `CCHK_*` overrides | You want the fastest feedback and to stop bad commits before they are pushed; pair it with the Action, since hooks are opt-in | You want zero YAML and no Actions minutes; fork PRs get a check run without the [two-workflow pattern](docs/fork-pr-comments.md) (no PR comment, though) |
111
111
112
112
Most teams pair the pre-commit hook (fast, local) with the Action (enforced):
113
113
the hook catches a bad message before it is pushed, and the Action is why CI
@@ -330,7 +330,7 @@ action's own, that comment is later found and edited in place like any other.
0 commit comments