gist_id parameter
Get a gist revision
Path Parameters
Response
application/json
Response
Response
Gist Simple
Gist Simple
Show Child Parameters
Gist History
Show Child Parameters
Gist
Show Child Parameters
Simple User
Show Child Parameters
Path Parameters
List gists for a user
Lists public gists for the specified user:
Query Parameters
Only show notifications updated after the given time. This is a timestamp in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ
.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Path Parameters
Response
application/json
Response
Response
Base Gist
Simple User
Show Child Parameters
Simple User
Show Child Parameters
Path Parameters
Query Parameters
Create a blob
Path Parameters
Body
application/json
Body
The new blob’s content.
The encoding used for content
. Currently, "utf-8"
and "base64"
are supported.
Default:utf-8
Response
application/json
Response
Response
Short Blob
Short Blob
Path Parameters
Body
Get a blob
The content
in the response will always be Base64 encoded.
Note: This API supports blobs up to 100 megabytes in size.
Path Parameters
Response
application/json
Response
Response
Blob
Blob
Path Parameters
Create a commit
Creates a new Git commit object.
Signature verification object
The response will include a verification
object that describes the result of verifying the commit’s signature. The following fields are included in the verification
object:
Name | Type | Description |
---|---|---|
verified |
boolean |
Indicates whether GitHub considers the signature in this commit to be verified. |
reason |
string |
The reason for verified value. Possible values and their meanings are enumerated in table below. |
signature |
string |
The signature that was extracted from the commit. |
payload |
string |
The value that was signed. |
These are the possible values for reason
in the verification
object:
Value | Description |
---|---|
expired_key |
The key that made the signature is expired. |
not_signing_key |
The “signing” flag is not among the usage flags in the GPG key that made the signature. |
gpgverify_error |
There was an error communicating with the signature verification service. |
gpgverify_unavailable |
The signature verification service is currently unavailable. |
unsigned |
The object does not include a signature. |
unknown_signature_type |
A non-PGP signature was found in the commit. |
no_user |
No user was associated with the committer email address in the commit. |
unverified_email |
The committer email address in the commit was associated with a user, but the email address is not verified on her/his account. |
bad_email |
The committer email address in the commit is not included in the identities of the PGP key that made the signature. |
unknown_key |
The key that made the signature has not been registered with any user’s account. |
malformed_signature |
There was an error parsing the signature. |
invalid |
The signature could not be cryptographically verified using the key whose key-id was found in the signature. |
valid |
None of the above errors applied, so the signature is considered to be verified. |
Path Parameters
Body
application/json
Body
The commit message
The SHA of the tree object this commit points to
The SHAs of the commits that were the parents of this commit. If omitted or empty, the commit will be written as a root commit. For a single parent, an array of one SHA should be provided; for a merge commit, an array of more than one should be provided.
Information about the author of the commit. By default, the author
will be the authenticated user and the current date. See the author
and committer
object below for details.
Show Child Parameters
Information about the person who is making the commit. By default, committer
will use the information set in author
. See the author
and committer
object below for details.
Show Child Parameters
The PGP signature of the commit. GitHub adds the signature to the gpgsig
header of the created commit. For a commit signature to be verifiable by Git or GitHub, it must be an ASCII-armored detached PGP signature over the string commit as it would be written to the object database. To pass a signature
parameter, you need to first manually create a valid PGP signature, which can be complicated. You may find it easier to use the command line to create signed commits.
Response
application/json
Response
Response
Git Commit
Low-level Git commit operations within a repository
SHA for the commit
Example:7638417db6d59f3c431d3e1f261cc637155684cd
Identifying information for the git-user
Show Child Parameters
Identifying information for the git-user
Show Child Parameters
Message describing the purpose of the commit
Example:Fix #42