Set Team Repo Permissions
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}.
For more information about the permission levels, see "Repository permission levels for an organization".
To learn more, visit the GitHub documentation.
Parameters
| Parameter | Description |
|---|---|
| Org | The organization name. The name is not case sensitive. |
| Owner | The account owner of the repository. The name is not case sensitive. |
| Permission | The permission to grant the team on this repository. In addition to the enumerated values, 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. |
| Repo | The name of the repository. The name is not case sensitive. |
| Team Slug | The slug of the team name. |
Automation Library Example
Set Team Repo Permissions with Github and Send Results Via Email
Preview this Automation on desktop