Note: The Nested Teams API is currently available for developers to preview. See the blog post for full details. To access the API, you must provide a custom media type in the Accept header:
application/vnd.github.hellcat-preview+json
Warning: The API may change without advance notice during the preview period. Preview features are not supported for production use. If you experience any issues, contact your GitHub Enterprise site administrator.
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.
PUT /teams/:team_id/repos/:owner/:repo
| Name | Type | Description |
|---|---|---|
permission |
string |
The permission to grant the team on this repository. Can be one of: * pull - team members can pull, but not push to or administer this repository.* push - team members can pull and push, but not administer this repository.* admin - team members can pull, push and administer 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. Note: If you pass the hellcat-preview media type, you can promote—but not demote—a permission attribute inherited through a parent team. |
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."
Status: 204 No Content