Actions
Delete a cache by id
Delete one cache entry by its id, as list_caches gives it.
DELETE
/repos/{owner}/{name}/actions/caches/{id}Over REST it answers 204 with no body, as GitHub does. Needs the Write role.
Answers 204 with no body.
- Authentication: Required. Send an access token as
Authorization: Bearer. - MCP tool:
workflowwithactiondelete_cache, and the same inputs - Scope: An access token needs
workflows:write.
Path parameters
Section titled “Path parameters”| Name | Type | Required | Description |
|---|---|---|---|
owner |
string | Yes | The workspace that owns the repository. |
name |
string | Yes | The repository’s name. |
id |
integer or string | Yes | The entry’s id, a number. |
Example request
Section titled “Example request”curl -X DELETE https://api.g1t.sh/repos/flagon-io/g1t/actions/caches/9102 \ -H "Authorization: Bearer $G1T_TOKEN"Example response
Section titled “Example response”A successful request answers 200.
Errors
Section titled “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 a token without the scope it needs. |
| 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. |