Skip to content

List the statuses on a commit, named by its SHA, a branch or a tag: one per context, newest first.

GET/repos/{owner}/{name}/commits/{ref}/statuses

Check runs are listed by list_check_runs_for_ref instead.

  • Authentication: Optional. Public data can be read without a token; send one to see what is private.
  • MCP tool: workflow with action list_statuses, and the same inputs
  • Scope: An access token needs checks:read.
Name Type Required Description
owner string Yes The workspace that owns the repository.
name string Yes The repository’s name.
ref string Yes The commit: its SHA, a branch or a tag.
curl https://api.g1t.sh/repos/flagon-io/hello/commits/main/statuses \
-H "Authorization: Bearer $G1T_TOKEN"

A successful request answers 200 with:

[
{
"context": "ci/build",
"state": "success",
"description": "Build #4821 passed",
"target_url": "https://ci.example.com/builds/4821",
"updated_at": "2026-10-07T14:03:02.118Z",
"source": "api"
}
]

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status Code When
401 unauthenticated A token is required, or the one sent is not valid.
403 forbidden The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404 not_found It does not exist, or you cannot see it.
422 invalid The input is not valid. message says which field and why.