Run protection

Turn a repository's workflows on or off

Turn a repository's workflows on or off (enabled).

PUT/repos/{owner}/{name}/actions/permissions

Off, nothing starts a run, and a dispatch or re-run is refused with “Actions is turned off for owner/name”; runs already going finish. Turning it on runs nothing by itself: the next event does. Needs the Admin role; a workflow job’s own token cannot.

Needs the Admin role (403 otherwise); a workflow job’s own token is refused. Turning workflows on starts nothing by itself. See Turn workflows off.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workflow with action set_enabled, and the same inputs
Scope: An access token needs repo:admin.

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
`enabled`	boolean	Yes	Whether its workflows run.

Example request

curl -X PUT https://api.g1t.sh/repos/ada/hello/actions/permissions \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true
  }'

Example response

A successful request answers 200 with:

{
  "enabled": true,
  "enabled_chosen": true,
  "allowed_actions": "all"
}

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.