Get runner settings for a workspace

Where a workspace's (or a repository's) g1t agent work runs, and whether pull requests from forks may use its self-hosted runners.

GET/workspaces/{workspace}/actions/runner-settings

agents_on_self_hosted sends agent runs, checks, reviews and the merge queue to runners with agent_labels instead of g1t’s sandboxes. A repository’s are its workspace’s unless it has its own (inherited).

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workflow with action get_runner_settings, and the same inputs
Scope: An access token needs runners:read.
Also at: GET /repos/{owner}/{name}/actions/runner-settings

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	Instead of repo: the workspace, for the runners its repositories share.

Example request

curl https://api.g1t.sh/workspaces/flagon-io/actions/runner-settings \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "agents_on_self_hosted": true,
  "agent_labels": [
    "self-hosted",
    "linux"
  ],
  "fork_pull_requests": false,
  "inherited": false
}

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.