release_id parameter
Update a release
Users with push access to the repository can edit a release.
Path Parameters
Body
application/json
Body
The name of the tag.
Specifies the commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. Unused if the Git tag already exists. Default: the repository’s default branch (usually master
).
The name of the release.
Text describing the contents of the tag.
true
makes the release a draft, and false
publishes the release.
true
to identify the release as a prerelease, false
to identify the release as a full release.
Response
200 application/json
Response
Response
Release
A release.
The name of the tag.
Example:v1.0.0
Specifies the commitish value that determines where the Git tag is created from.
Example:master
true to create a draft (unpublished) release, false to create a published one.
Example:false
Whether to identify the release as a prerelease or a full release.
Example:false
Simple User
Show Child Parameters
Data related to a release.
Show Child Parameters
Show Child Parameters
Path Parameters
Body
Delete a release
Users with push access to the repository can delete a release.
Path Parameters
release_id parameter
Response
204
Response
Response
Path Parameters
List release assets
Query Parameters
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Path Parameters
release_id parameter
Response
200 application/json
Response
Response
Data related to a release.
The file name of the asset.
Example:Team Environment
State of the release asset.
Allowed values:uploadedopen
Simple User
Show Child Parameters
Path Parameters
Query Parameters
Upload a release asset
This endpoint makes use of a Hypermedia relation to determine which URL to access. The endpoint you call to upload release assets is specific to your release. Use the upload_url
returned in
the response of the Create a release endpoint to upload a release asset.
You need to use an HTTP client which supports SNI to make calls to this endpoint.
Most libraries will set the required Content-Length
header automatically. Use the required Content-Type
header to provide the media type of the asset. For a list of media types, see Media Types. For example:
application/zip
GitHub Enterprise Server expects the asset data in its raw binary form, rather than JSON. You will send the raw binary content of the asset as the request body. Everything else about the endpoint is the same as the rest of the API. For example,
you’ll still need to pass your authentication to be able to upload an asset.
When an upstream failure occurs, you will receive a 502 Bad Gateway
status. This may leave an empty asset with a state of starter
. It can be safely deleted.
Notes:
- GitHub Enterprise Server renames asset filenames that have special characters, non-alphanumeric characters, and leading or trailing periods. The “List assets for a release”
endpoint lists the renamed filenames. For more information and help, contact GitHub Enterprise Server Support. - If you upload an asset with the same filename as another uploaded asset, you’ll receive an error and must delete the old file before you can re-upload the new asset.
Query Parameters
Path Parameters
release_id parameter
Body
*/*
Body
The raw file data
Response
application/json
Response
Response for successful upload
Release Asset
Data related to a release.
The file name of the asset.
Example:Team Environment
State of the release asset.
Allowed values:uploadedopen
Simple User
Show Child Parameters
Path Parameters
Query Parameters
Body
Get the weekly commit activity
Returns a weekly aggregate of the number of additions and deletions pushed to a repository.
Path Parameters
Response
application/json
Response
Returns a weekly aggregate of the number of additions and deletions pushed to a repository.
Code Frequency Stat