Remove a repository's Actions access to a package

DELETE/workspaces/{workspace}/packages/{package_type}/{package_name}/actions-access/{repository}

The linked repository’s access cannot be removed: unlink the package instead. Takes the Admin role on the package. Returns the package’s Actions access.

• Authentication: Required. Send an access token as Authorization: Bearer.
• MCP tool: package with action remove_actions_access, and the same inputs
• Scope: An access token needs packages:write.

Path parameters

Name	Type	Required	Description
workspace	string	Yes	The workspace’s slug, e.g. “flagon-io”.
package_type	string	Yes	The registry: container (also docker), npm, cargo, maven, nuget, rubygems or composer. One of container, npm, cargo, maven, nuget, rubygems, composer.
package_name	string	Yes	The package’s name without the workspace: web for g1t.sh/acme/web, web/worker for an image with more parts, group:artifact for Maven.
repository	string	Yes	The repository: its name, or owner/name.

Example request

curl -X DELETE https://api.g1t.sh/workspaces/acme/packages/container/web/actions-access/deploy \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "repositories": [
    {
      "repository_id": "rep_01kpw0a2c4e6g8j0m2p4r6t8v0",
      "repository": "acme/web",
      "role": "write",
      "linked": true,
      "created_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.
409	conflict	The request conflicts with the current state.
422	invalid	The input is not valid. message says which field and why.