ghtier
← All permissions
Repository permission·checks:read

Checks: Read

Tier 3 · Low

Why Tier 3

Reads check runs and suites.

Data plane permissions start at Tier 2. This one is lowered for the reason above.

Target
Repository
Plane
DataCode: Repository contents, branches, tags, pull requests, checks and commit signing keys.
Granted by
GitHub App, GITHUB_TOKEN
Available on
Every setup
In a workflow
permissions: checks: read

What it unlocks

6 REST endpoints need this permission. A few of them:

  • GET /repos/{owner}/{repo}/check-runs/{check_run_id}
  • GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations
  • GET /repos/{owner}/{repo}/check-suites/{check_suite_id}
  • GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs

Roles that include it

No built-in role includes it. Only tokens, Apps or custom roles can grant it.

Classic scopes that reach it

Attack paths

No attack technique, escalation or incident on ghtier goes through this yet.

Other levels

GitHub Docs: Repository permissions for "Checks"