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
Path Parameters
Get the last year of commit activity
Returns the last year of commit activity grouped by week. The days
array is a group of commits per day, starting on Sunday
.
Path Parameters
Response
application/json
Response
Response
Commit Activity
Example:[0,3,26,20,39,1,0]
Example:89
Example:1336280400
Path Parameters
Get all contributor commit activity
Returns the total
number of commits authored by the contributor. In addition, the response includes a Weekly Hash (weeks
array) with the following information:
w
- Start of the week, given as a Unix timestamp.a
- Number of additionsd
- Number of deletionsc
- Number of commits
Path Parameters
Response
application/json
Response
w
- Start of the week, given as a Unix timestamp.a
- Number of additionsd
- Number of deletionsc
- Number of commits
Contributor Activity
Simple User
Show Child Parameters
Example:135
Example:[{"w":"1367712000","a":6898,"d":77,"c":10}]
Show Child Parameters
Path Parameters
Get the weekly commit count
Returns the total commit counts for the owner
and total commit counts in all
. all
is everyone combined, including the owner
in the last 52 weeks. If you’d like to get the commit counts for non-owners, you can subtract owner
from all
.
The array order is oldest week (index 0) to most recent week.
Path Parameters
Response
application/json
Response
The array order is oldest week (index 0) to most recent week.