Rerequest a check run

POST/repos/{owner}/{name}/check-runs/{id}/rerequest

For one reported through the API, its reporter is sent check_run.rerequested; for a g1t Actions job, its workflow run runs again (which also needs workflows:write). Needs the Write role.

• Authentication: Required. Send an access token as Authorization: Bearer.
• MCP tool: workflow with action rerequest_check_run, and the same inputs
• Scope: An access token needs checks:write.

Path parameters

Name	Type	Required	Description
owner	string	Yes	The workspace that owns the repository.
name	string	Yes	The repository’s name.
id	string	Yes	The check run’s id: cr_…, or a g1t Actions job’s job_…

Example request

curl -X POST https://api.g1t.sh/repos/flagon-io/hello/check-runs/cr_01kq4b7c8d9e0f1g2h3j4k5m6n/rerequest \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "rerequested": true
}

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.
409	conflict	The request conflicts with the current state.
422	invalid	The input is not valid. message says which field and why.