Get repository settings

How a repository handles pull requests: the approvals a merge needs, whether failed checks can be overridden, whether a pull request must be up to date, and how g1t's agents are reviewed, revised and merged.

GET/repos/{owner}/{name}/settings

Authentication: Optional. Public data can be read without a token; send one to see what is private.
MCP tool: get_repo_settings, 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.

Example request

curl https://api.g1t.sh/repos/flagon-io/hello/settings \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "auto_merge": false,
  "require_up_to_date": false,
  "required_approvals": 0,
  "count_agent_approvals": true,
  "allow_ignoring_checks": true,
  "agent_review": true,
  "max_revisions": 2,
  "merge_queue": false,
  "updated_by": null,
  "updated_at": null
}

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.