Add or update team repository permissions (Legacy)
[!WARNING] Endpoint closing down notice: This endpoint route is closing down 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 method.”
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”The unique identifier of the team.
The account owner of the repository. The name is not case sensitive.
The name of the repository without the .git extension. The name is not case sensitive.
Request Body
Section titled “ Request Body ”object
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.
Examples
Example of setting permission to pull
{ "permission": "push"}Responses
Section titled “ Responses ”Response
Forbidden
Basic Error
object
Example generated
{ "message": "example", "documentation_url": "example", "url": "example", "status": "example"}Validation failed, or the endpoint has been spammed.
Validation Error
object
object
Example generated
{ "message": "example", "documentation_url": "example", "errors": [ { "resource": "example", "field": "example", "message": "example", "code": "example", "index": 1, "value": [ "example" ] } ]}