Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Lists a team’s repositories visible to the authenticated user.
Note: You can also specify a team by org_id
and team_id
using the route GET /organizations/{org_id}/team/{team_id}/repos
.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
team_slug parameter
Response
Minimal Repository
Example:1296269
Example:MDEwOlJlcG9zaXRvcnkxMjk2MjY5
Example:Hello-World
Example:octocat/Hello-World
Simple User
Example:https://github.com/octocat/Hello-World
Example:This your first repo!
Example:https://api.github.com/repos/octocat/Hello-World
Example:http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}
Example:http://api.github.com/repos/octocat/Hello-World/assignees{/user}
Example:http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/branches{/branch}
Example:http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}
Example:http://api.github.com/repos/octocat/Hello-World/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}
Example:http://api.github.com/repos/octocat/Hello-World/contents/{+path}
Example:http://api.github.com/repos/octocat/Hello-World/contributors
Example:http://api.github.com/repos/octocat/Hello-World/deployments
Example:http://api.github.com/repos/octocat/Hello-World/downloads
Example:http://api.github.com/repos/octocat/Hello-World/events
Example:http://api.github.com/repos/octocat/Hello-World/forks
Example:http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues/events{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues{/number}
Example:http://api.github.com/repos/octocat/Hello-World/keys{/key_id}
Example:http://api.github.com/repos/octocat/Hello-World/labels{/name}
Example:http://api.github.com/repos/octocat/Hello-World/languages
Example:http://api.github.com/repos/octocat/Hello-World/merges
Example:http://api.github.com/repos/octocat/Hello-World/milestones{/number}
Example:http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}
Example:http://api.github.com/repos/octocat/Hello-World/pulls{/number}
Example:http://api.github.com/repos/octocat/Hello-World/releases{/id}
Example:http://api.github.com/repos/octocat/Hello-World/stargazers
Example:http://api.github.com/repos/octocat/Hello-World/statuses/{sha}
Example:http://api.github.com/repos/octocat/Hello-World/subscribers
Example:http://api.github.com/repos/octocat/Hello-World/subscription
Example:http://api.github.com/repos/octocat/Hello-World/tags
Example:http://api.github.com/repos/octocat/Hello-World/teams
Example:http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/hooks
Example:2011-01-26T19:06:43Z
Example:2011-01-26T19:01:12Z
Example:2011-01-26T19:14:43Z
A git repository
Code Of Conduct
Example:0
Example:0
Example:0
Checks whether a team has admin
, push
, maintain
, triage
, or pull
permission for a repository. Repositories inherited through a parent team will also be checked.
You can also get information about the specified repository, including what permissions the team grants on it, by passing the following custom media type via the application/vnd.github.v3.repository+json
accept header.
If a team doesn’t have permission for the repository, you will receive a 404 Not Found
response status.
Note: You can also specify a team by org_id
and team_id
using the route GET /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}
.
team_slug parameter
Alternative response with repository permissions
A team’s access to a repository.
Unique identifier of the repository
Example:42
Example:MDEwOlJlcG9zaXRvcnkxMjk2MjY5
The name of the repository.
Example:Team Environment
Example:octocat/Hello-World
License Simple
Simple User
Whether the repository is private or public.
Default:false
Example:https://github.com/octocat/Hello-World
Example:This your first repo!
Example:https://api.github.com/repos/octocat/Hello-World
Example:http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}
Example:http://api.github.com/repos/octocat/Hello-World/assignees{/user}
Example:http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/branches{/branch}
Example:http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}
Example:http://api.github.com/repos/octocat/Hello-World/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}
Example:http://api.github.com/repos/octocat/Hello-World/contents/{+path}
Example:http://api.github.com/repos/octocat/Hello-World/contributors
Example:http://api.github.com/repos/octocat/Hello-World/deployments
Example:http://api.github.com/repos/octocat/Hello-World/downloads
Example:http://api.github.com/repos/octocat/Hello-World/events
Example:http://api.github.com/repos/octocat/Hello-World/forks
Example:http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}
Example:git:github.com/octocat/Hello-World.git
Example:http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues/events{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues{/number}
Example:http://api.github.com/repos/octocat/Hello-World/keys{/key_id}
Example:http://api.github.com/repos/octocat/Hello-World/labels{/name}
Example:http://api.github.com/repos/octocat/Hello-World/languages
Example:http://api.github.com/repos/octocat/Hello-World/merges
Example:http://api.github.com/repos/octocat/Hello-World/milestones{/number}
Example:http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}
Example:http://api.github.com/repos/octocat/Hello-World/pulls{/number}
Example:http://api.github.com/repos/octocat/Hello-World/releases{/id}
Example:git@github.com:octocat/Hello-World.git
Example:http://api.github.com/repos/octocat/Hello-World/stargazers
Example:http://api.github.com/repos/octocat/Hello-World/statuses/{sha}
Example:http://api.github.com/repos/octocat/Hello-World/subscribers
Example:http://api.github.com/repos/octocat/Hello-World/subscription
Example:http://api.github.com/repos/octocat/Hello-World/tags
Example:http://api.github.com/repos/octocat/Hello-World/teams
Example:http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}
Example:https://github.com/octocat/Hello-World.git
Example:git:git.example.com/octocat/Hello-World
Example:http://api.github.com/repos/octocat/Hello-World/hooks
Example:https://svn.github.com/octocat/Hello-World
Example:https://github.com
Example:9
Example:80
Example:80
Example:108
The default branch of the repository.
Example:master
Example:0
Whether this repository acts as a template that can be used to generate new repositories.
Default:false
Example:true
Whether issues are enabled.
Default:true
Example:true
Whether projects are enabled.
Default:true
Example:true
Whether the wiki is enabled.
Default:true
Example:true
Whether downloads are enabled.
Default:true
Example:true
Whether the repository is archived.
Default:false
Returns whether or not this repository disabled.
The repository visibility: public, private, or internal.
Default:public
Example:2011-01-26T19:06:43Z
Example:2011-01-26T19:01:12Z
Example:2011-01-26T19:14:43Z
Whether to allow rebase merges for pull requests.
Default:true
Example:true
A git repository
Whether to allow squash merges for pull requests.
Default:true
Example:true
Whether to delete head branches when pull requests are merged
Default:false
Example:false
Whether to allow merge commits for pull requests.
Default:true
Example:true
Whether to allow forking this repo
Default:false
Example:false
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”.
team_slug parameter
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.
Allowed values:pullpushadminmaintaintriage
Default:push
Response
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. This does not delete the repository, it just removes it from the team.
Note: You can also specify a team by org_id
and team_id
using the route DELETE /organizations/{org_id}/team/{team_id}/repos/{owner}/{repo}
.
team_slug parameter
Response
Lists the child teams of the team specified by {team_slug}
.
Note: You can also specify a team by org_id
and team_id
using the route GET /organizations/{org_id}/team/{team_id}/teams
.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
team_slug parameter
if child teams exist
Groups of organization members that gives permissions on specified repositories.
Example:https://github.com/orgs/rails/teams/core
Groups of organization members that gives permissions on specified repositories.