Add or update team repository permissions (Legacy)

Deprecated

PUT

/teams/{team_id}/repos/{owner}/{repo}

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new "Add or update team repository permissions" endpoint.

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 verbs."

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://api.github.com/teams//repos//' \
--header 'Content-Type: application/json' \
--data-raw '{
    "permission": "push"
}'

Response Example

204 - Example 1

{}

Request

Path Params

team_id

integer

required

The unique identifier of the team.

owner

string

required

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

repo

string

required

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

Body Params application/json

permission

enum<string>

optional

The permission to grant the team on this repository. If no permission is specified, the team's permission attribute will be used to determine what permission to grant the team on this repository.

Allowed values:

pullpushadmin

Examples

Responses

🟢204Response

application/json

Body

object {0}

🟠403403

🟠422422

Modified at 2023-08-15 02:59:30

Check team permissions for a repository (Legacy)

List child teams (Legacy)