Add or update team repository permissions (Legacy)
DEPRECATEDDeprecation 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.”
Path Parameters
Body
application/json
Body
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.
Allowed values:pullpushadmin
Response
Response
Response
Path Parameters
Body
Remove a repository from a team (Legacy)
DEPRECATEDDeprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Remove a repository from a team endpoint.
If the authenticated user is an organization owner or a team maintainer, they can remove any repositories from the team. To remove a repository from a team as an organization member, the authenticated user must have admin access to the repository and must be able to see the team. NOTE: This does not delete the repository, it just removes it from the team.
Path Parameters
Response
204
Response
Response
Path Parameters
List child teams (Legacy)
DEPRECATEDDeprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new List child teams
endpoint.
Query Parameters
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Path Parameters
Response
application/json
Response
if child teams exist
Groups of organization members that gives permissions on specified repositories.
Show Child Parameters
Example:https://github.com/orgs/rails/teams/core
Groups of organization members that gives permissions on specified repositories.
Show Child Parameters
Path Parameters
Query Parameters
List teams for the authenticated user
Query Parameters
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
application/json
Response
Response
Groups of organization members that gives permissions on specified repositories.
Unique identifier of the team
Example:42
Example:MDQ6VGVhbTE=
URL for the team
Example:https://api.github.com/organizations/1/team/1
Example:https://github.com/orgs/rails/teams/core
Name of the team
Example:Developers
Example:justice-league
Example:A great team.
The level of privacy this team should have
Allowed values:closedsecret
Example:closed
Permission that the team will have for its repositories
Example:push
Example:https://api.github.com/organizations/1/team/1/members{/member}
Example:https://api.github.com/organizations/1/team/1/repos
Groups of organization members that gives permissions on specified repositories.
Show Child Parameters
Example:3
Example:10
Example:2017-07-14T16:53:42Z
Example:2017-08-17T12:37:15Z
Organization Full
Show Child Parameters
Distinguished Name (DN) that team maps to within LDAP environment
Example:uid=example,ou=users,dc=github,dc=com
Query Parameters
Get the authenticated user
If the authenticated user is authenticated through basic authentication or OAuth with the user
scope, then the response lists public and private profile information.
If the authenticated user is authenticated through OAuth without the user
scope, then the response lists only public profile information.
Response
application/json
Response
Response
One Of
Example:octocat
Example:1
Example:MDQ6VXNlcjE=
Example:https://github.com/images/error/octocat_happy.gif
Example:41d064eb2195891e12d0413f63227ea7
Example:https://api.github.com/users/octocat
Example:https://github.com/octocat
Example:https://api.github.com/users/octocat/followers
Example:https://api.github.com/users/octocat/following{/other_user}
Example:https://api.github.com/users/octocat/gists{/gist_id}
Example:https://api.github.com/users/octocat/starred{/owner}{/repo}
Example:https://api.github.com/users/octocat/subscriptions
Example:https://api.github.com/users/octocat/orgs
Example:https://api.github.com/users/octocat/repos
Example:https://api.github.com/users/octocat/events{/privacy}
Example:https://api.github.com/users/octocat/received_events
Example:User
Example:monalisa octocat
Example:GitHub
Example:https://github.com/blog
Example:San Francisco
Example:octocat@github.com
Example:There once was...
Example:2
Example:1
Example:20
Example:0
Example:2008-01-14T04:33:35Z
Example:2008-01-14T04:33:35Z
Example:81
Example:100
Example:100
Example:10000
Example:8
Example:true