[tylerpaxton]

What

This PR adds a Read results with the GitHub API section to content/chainguard/checks/github.md and mentions it in the page's intro. The section covers:

• The GitHub access the API needs. It doesn't need a Chainguard role, so it also works with the limited_owner role in a Starter organization.
• How to read the summary check on a pull request's head commit with the GitHub CLI, and which fields to act on.
• When a result goes out of date: after a rerun, a ci/run: label, a change to the pull request, or a push.
• How each check's outcome maps to its check run's conclusion, and why only the summary check decides whether a pull request passes.

Why

Merge bots, dashboards, and agents read Chainguard Checks results through GitHub's REST API. The page didn't say where results appear, which conclusion to act on, or which per-check results can be missing or out of date.

How it was checked

• Checked each behavior against the Chainguard Checks source: per-check conclusions, the 50-row limit on the summary table, check runs that an earlier run leaves behind, and what happens to unfinished checks after Run failed.
• Checked token requirements against GitHub's REST API docs for check runs and its list of permissions for fine-grained personal access tokens, which has no Checks permission.
• Ran the example against a live pull request. It returned the summary check's status, conclusion, and title. An empty result prints every field as null, as the page says.
• Ran the repository's pre-commit hooks and markdownlint-cli2 on the page. Both pass.
• Confirmed that every internal link and anchor on the page resolves.

For reviewers

The section tells a merge bot to find the summary check by name. Another app or a workflow job could create a check run with the same name. The section doesn't yet say how to confirm which app created a check run, because the app's identity isn't a stable contract yet. That guidance waits for engineering to confirm.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
chainguard-docs-preview	Ready	Preview	Oct 20, 2026 6:09pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
chainguard-docs	Ignored		Oct 20, 2026 6:09pm UTC

[matthewhelmke]

This is clear to me and fills a gap nicely. Thank you!!