Skip to main content

legacy_repos

Overview

Namelegacy_repos
TypeResource
Idgithub.teams.legacy_repos

Fields

NameDatatypeDescription
idinteger
namestring
descriptionstring
forks_countinteger
statuses_urlstring
has_wikiboolean
is_templateboolean
disabledboolean
compare_urlstring
watchersinteger
git_commits_urlstring
deployments_urlstring
subscribers_countinteger
tags_urlstring
blobs_urlstring
sizeinteger
labels_urlstring
code_of_conductobjectCode Of Conduct
contents_urlstring
events_urlstring
commits_urlstring
has_pagesboolean
visibilitystring
git_urlstring
temp_clone_tokenstring
role_namestring
pushed_atstring
clone_urlstring
updated_atstring
teams_urlstring
html_urlstring
branches_urlstring
forksinteger
downloads_urlstring
homepagestring
collaborators_urlstring
trees_urlstring
open_issuesinteger
forkboolean
created_atstring
mirror_urlstring
releases_urlstring
merges_urlstring
watchers_countinteger
git_refs_urlstring
stargazers_urlstring
open_issues_countinteger
issue_comment_urlstring
node_idstring
stargazers_countinteger
keys_urlstring
issue_events_urlstring
ownerobjectSimple User
licenseobject
urlstring
has_issuesboolean
delete_branch_on_mergeboolean
topicsarray
issues_urlstring
languagestring
full_namestring
permissionsobject
forks_urlstring
subscription_urlstring
allow_forkingboolean
hooks_urlstring
network_countinteger
pulls_urlstring
svn_urlstring
default_branchstring
comments_urlstring
privateboolean
archive_urlstring
subscribers_urlstring
milestones_urlstring
contributors_urlstring
assignees_urlstring
languages_urlstring
has_projectsboolean
template_repositoryobjectA git repository
notifications_urlstring
has_downloadsboolean
archivedboolean
ssh_urlstring
git_tags_urlstring

Methods

NameAccessible byRequired ParamsDescription
list_repos_legacySELECTteam_idDeprecation 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 team repositories endpoint.
remove_repo_legacyDELETEowner, repo, team_idDeprecation 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.
add_or_update_repo_permissions_legacyEXECowner, repo, team_idDeprecation 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."
check_permissions_for_repo_legacyEXECowner, repo, team_idNote: Repositories inherited through a parent team will also be checked.

Deprecation Notice: This endpoint route is deprecated and will be removed from the Teams API. We recommend migrating your existing code to use the new Check team permissions for a repository endpoint.

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 Accept header: