From 7391cd088795979d2b4a3ba77d35500038fd7c84 Mon Sep 17 00:00:00 2001 From: Xianpeng Shen Date: Fri, 25 Sep 2026 23:32:11 +0300 Subject: [PATCH] docs: link the App's install page, not its Marketplace listing github.com/marketplace/commit-check is a 404 for anyone who is not signed in while the listing is still under review, which it has been since 2026-09-02. github.com/apps/commit-check is public and installs the same App, so the links point there until the listing is live. --- README.md | 4 ++-- docs/fork-pr-comments.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 48947615..bc972c29 100644 --- a/README.md +++ b/README.md @@ -103,7 +103,7 @@ All three run the same `commit-check` engine against the same `commit-check.toml` / `cchk.toml`; they differ in where they run and what they can see. -| | GitHub Action (this repo) | [pre-commit hook](https://github.com/commit-check/commit-check#use-with-pre-commit) | [Commit Check GitHub App](https://github.com/marketplace/commit-check) | +| | GitHub Action (this repo) | [pre-commit hook](https://github.com/commit-check/commit-check#use-with-pre-commit) | [Commit Check GitHub App](https://github.com/apps/commit-check) | |---|---|---|---| | **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 | | **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` output | 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 | @@ -523,7 +523,7 @@ By default, commit-check-action handles this gracefully: > **For most projects, this is sufficient** — a fork contributor already gets the red > check, the per-finding annotations on their diff and the full report in the job > summary. If you want feedback on the pull request itself, the -> [Commit Check GitHub App](https://github.com/marketplace/commit-check) posts a check +> [Commit Check GitHub App](https://github.com/apps/commit-check) posts a check > run per commit with no workflow file (free on public repositories), or you can run > this action on `pull_request_target`. Both are covered in > **[Fork pull requests](docs/fork-pr-comments.md)**. diff --git a/docs/fork-pr-comments.md b/docs/fork-pr-comments.md index 204fa8af..926b42b8 100644 --- a/docs/fork-pr-comments.md +++ b/docs/fork-pr-comments.md @@ -34,7 +34,7 @@ The run is **not** failed by this: `pr-comments: true` on a fork PR is a no-op, ### Install the Commit Check GitHub App (recommended) -The [Commit Check GitHub App](https://github.com/marketplace/commit-check) is not bound by +The [Commit Check GitHub App](https://github.com/apps/commit-check) is not bound by the `pull_request` token at all: it receives the `pull_request` webhook on the **base** repository and acts with its own installation token. Fork pull requests are ordinary pull requests to it.