ghtier
← All permissions
Repository permission·statuses:read

Commit statuses: Read

Tier 3 · Low

Why Tier 3

Reads commit statuses.

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
Fine-grained PAT, GitHub App, GITHUB_TOKEN
Available on
Every setup
In a workflow
permissions: statuses: read

What it unlocks

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

  • GET /repos/{owner}/{repo}/commits/{ref}/status
  • GET /repos/{owner}/{repo}/commits/{ref}/statuses

Roles that include it

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

Classic scopes that reach it

No classic scope reaches it. Only fine-grained PATs, Apps or GITHUB_TOKEN can grant it.

Attack paths

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

Other levels

GitHub Docs: Repository permissions for "Commit statuses"