Remove a team from a repository

Take a team's role on a repository away.

DELETE/workspaces/{workspace}/teams/{team}/repos/{repo}

Its people keep only the roles they have otherwise. Needs the Admin role on the repository, or to be an owner or one of the team’s maintainers. People only. Returns true.

A role the team inherits from a parent is taken away on the parent. Needs the Admin role on the repository, or to be an owner or one of the team’s maintainers.

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

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.
`team`	string	Yes	The team’s slug, as in its mention @workspace/slug, e.g. “backend”.
`repo`	string	Yes	The repository, in the team’s workspace: its name, or “owner/name”.

Example request

curl -X DELETE https://api.g1t.sh/workspaces/flagon-io/teams/backend/repos/hello \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

true

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.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.