GET
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
PUT
DELETE
GET
GET
GET
PUT
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
DELETE
GET
PATCH
DELETE
GET
POST
PUT
DELETE
GET
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
GET
POST
PUT
DELETE
POST
GET
GET
PUT
DELETE
GET
GET
GET
PATCH
DELETE
GET
GET
GET
POST
GET
GET
GET
GET
GET
GET
GET
PUT
DELETE
GET
GET
POST
GET
DELETE
GET
POST
GET
POST
GET
GET
PUT
DELETE
GET
POST
GET
POST
GET
PATCH
DELETE
GET
PATCH
GET
GET
POST
POST
POST
GET
PATCH
DELETE
GET
POST
GET
DELETE
GET
PUT
DELETE
POST
POST
GET
POST
PUT
DELETE
GET
POST
GET
GET
GET
GET
GET
GET
POST
GET
PATCH
DELETE
POST
GET
GET
GET
PATCH
DELETE
GET
POST
GET
GET
GET
GET
GET
POST
GET
GET
GET
GET
PUT
GET
GET
GET
GET
POST
GET
PUT
DELETE
GET
POST
GET
GET
POST
GET
PATCH
DELETE
GET
Creates a new repository using a repository template. Use the template_owner
and template_repo
route parameters to specify the repository to use as the template. The authenticated user must own or be a member of an organization that owns the repository. To check if a repository is available to use as a template, get the repository's information using the Get a repository endpoint and check that the is_template
key is true
.
OAuth scope requirements
When using OAuth, authorizations must include:
public_repo
scope or repo
scope to create a public repository. Note: For GitHub AE, use repo
scope to create an internal repository.repo
scope to create a private repository