Skip to content

Move a mirror to g1t for good: it stops being a mirror and g1t no longer tracks the remote, so pushes made there no longer come here.

POST/repos/{owner}/{name}/mirror/move-to-g1t

Allowed while it stands by, in CI failover, or during a takeover, whose work stays as it is. With keep_remote_updated: true the remote becomes a follower instead of being unlinked, and g1t pushes to it from then on. Needs the Admin role; agents’ tokens are refused.

With keep_remote_updated: true the remote stays in remotes as a follower, and g1t pushes to it from then on.

  • Authentication: Required. Send an access token as Authorization: Bearer.
  • MCP tool: repository with action mirror_move_to_g1t, and the same inputs
  • Scope: An access token needs repo:admin.
Name Type Required Description
owner string Yes The workspace that owns the repository.
name string Yes The repository’s name.

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

Name Type Required Description
keep_remote_updated boolean No True to keep pushing to the remote from g1t; false (the default) to stop tracking it.
curl -X POST https://api.g1t.sh/repos/acme/web/mirror/move-to-g1t \
-H "Authorization: Bearer $G1T_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"keep_remote_updated": false
}'

A successful request answers 200 with:

{
"remotes": [],
"plan": null,
"can_manage": true
}

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.