Add or update team repository permissions

PUT

/orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}

To add a repository to a team or update the team’s permission on a repository, the authenticated user must have admin access to the repository, and must be able to see the team. The repository must be owned by the organization, or a direct fork of a repository owned by the organization. You will get a 422 Unprocessable Entity status if you attempt to add a repository to a team that is not owned by the organization. Note that, if you choose not to pass any parameters, you’ll need to set Content-Length to zero when calling out to this endpoint. For more information, see “HTTP method.”

[!NOTE] You can also specify a team by org_id and team_id using the route PUT /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}.

For more information about the permission levels, see “Repository permission levels for an organization”.

API method documentation

Parameters

Path Parameters

org

required

string

The organization name. The name is not case sensitive.

team_slug

required

string

The slug of the team name.

owner

required

string

The account owner of the repository. The name is not case sensitive.

repo

required

string

The name of the repository without the .git extension. The name is not case sensitive.

Request Body

Media type application/json

object

permission

The permission to grant the team on this repository. We accept the following permissions to be set: pull, triage, push, maintain, admin and you can also specify a custom repository role name, if the owning organization has defined any. If no permission is specified, the team’s permission attribute will be used to determine what permission to grant the team on this repository.

string

Examples

Example default

Adding a team to an organization repository with the write role

{
  "permission": "push"
}

Responses

204

Response