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."
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.
PUT /orgs/:org/teams/:team_slug/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.* maintain - team members can manage the repository without access to sensitive or destructive actions. Recommended for project managers. Only applies to repositories owned by organizations. * triage - team members can proactively manage issues and pull requests without write access. Recommended for contributors who triage a repository. Only applies to repositories owned by organizations.If no permission is specified, the team's permission attribute will be used to determine what permission to grant the team on this repository. |
For more information about the permission levels, see "Repository permission levels for an organization" in the GitHub Help documentation.
Status: 204 No Content