Purge a deleted repository

Permanently remove a deleted repository now, instead of waiting for its 30 days to end.

POST/repos/{owner}/{name}/purge

Owners only, and confirm must be its full name, owner/name. Its git data, issues, pull requests, deployments and custom domains are removed and cannot be recovered, and its name is free to use again.

Permanent: it cannot be restored afterwards, and its name is free again. Only a deleted repository can be purged (404 otherwise). Owners only (403); 422 when confirm is not its full name.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: purge_repo, with the same inputs

Path parameters

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

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`confirm`	string	Yes	Its full name, owner/name, typed out, to confirm.

Example request

curl -X POST https://api.g1t.sh/repos/flagon-io/hello/purge \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "confirm": "flagon-io/hello"
  }'

Example response

A successful request answers 200 with:

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.