List check names

The check names reported on a repository's commits in the last 30 days, most recent first, with the events each was reported for: the names update_repo_settings takes in required_checks.

GET/repos/{owner}/{name}/check-names

A workflow’s runs report a check named after the workflow; a check required on the default branch must be reported on a pull request’s head (pull_request events) and, with the merge queue on, on its queued state (merge_group events).

The names reported on the repository’s commits in the last 30 days, most recent first. A workflow reports a check named after it (CI), for each event it ran for; another tool, such as a deployment, reports its own name (g1t / deploy). Empty until something has reported on a commit: add a workflow in .g1t/workflows first.

Authentication: Optional. Public data can be read without a token; send one to see what is private.
MCP tool: repository with action check_names, and the same inputs
Scope: An access token needs repo:read.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.

Example request

curl https://api.g1t.sh/repos/flagon-io/hello/check-names \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "name": "CI",
    "events": [
      "pull_request",
      "merge_group",
      "push"
    ],
    "last_seen": "2026-10-06T09:14:02.118Z"
  },
  {
    "name": "g1t / deploy",
    "events": [],
    "last_seen": "2026-10-06T08:51:40.006Z"
  }
]

Errors

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.