You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/actions/deleteSelfHostedRunnerFromOrg.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ type: API method
8
8
9
9
# Delete a self-hosted runner from an organization
10
10
11
-
**Warning:** The self-hosted runners API for organizations is currently in public beta and subject to change.
11
+
Forces the removal of a self-hosted runner from an organization. You can use this endpoint to completely remove the runner when the machine you were using no longer exists.
12
12
13
-
Forces the removal of a self-hosted runner from an organization. You can use this endpoint to completely remove the runner when the machine you were using no longer exists. You must authenticate using an access token with the `admin:org` scope to use this endpoint.
13
+
You must authenticate using an access token with the `admin:org` scope to use this endpoint.
Copy file name to clipboardexpand all lines: docs/actions/deleteSelfHostedRunnerFromRepo.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,10 @@ type: API method
8
8
9
9
# Delete a self-hosted runner from a repository
10
10
11
-
Forces the removal of a self-hosted runner from a repository. You can use this endpoint to completely remove the runner when the machine you were using no longer exists. You must authenticate using an access token with the `repo` scope to use this endpoint.
11
+
Forces the removal of a self-hosted runner from a repository. You can use this endpoint to completely remove the runner when the machine you were using no longer exists.
12
+
13
+
You must authenticate using an access token with the `repo`
Copy file name to clipboardexpand all lines: docs/actions/listRunnerApplicationsForOrg.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ type: API method
8
8
9
9
# List runner applications for an organization
10
10
11
-
**Warning:** The self-hosted runners API for organizations is currently in public beta and subject to change.
11
+
Lists binaries for the runner application that you can download and run.
12
12
13
-
Lists binaries for the runner application that you can download and run. You must authenticate using an access token with the `admin:org` scope to use this endpoint.
13
+
You must authenticate using an access token with the `admin:org` scope to use this endpoint.
Copy file name to clipboardexpand all lines: docs/actions/listRunnerApplicationsForRepo.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,9 @@ type: API method
8
8
9
9
# List runner applications for a repository
10
10
11
-
Lists binaries for the runner application that you can download and run. You must authenticate using an access token with the `repo` scope to use this endpoint.
11
+
Lists binaries for the runner application that you can download and run.
12
+
13
+
You must authenticate using an access token with the `repo` scope to use this endpoint.
The source branch and directory used to publish your Pages site.
36
42
37
43
</td></tr>
38
-
<tr><td>source.branch</td><td>no</td><td>
44
+
<tr><td>source.branch</td><td>yes</td><td>
39
45
40
-
The repository branch used to publish your [site's source files](https://docs.github.com/articles/configuring-a-publishing-source-for-github-pages/). Can be either `master` or `gh-pages`.
46
+
The repository branch used to publish your site's source files.
41
47
42
48
</td></tr>
43
49
<tr><td>source.path</td><td>no</td><td>
44
50
45
-
The repository directory that includes the source files for the Pages site. When `branch` is `master`, you can change `path` to `/docs`. When `branch` is `gh-pages`, you are unable to specify a `path` other than `/`.
51
+
The repository directory that includes the source files for the Pages site. Allowed paths are `/` or `/docs`. Default: `/`
Copy file name to clipboardexpand all lines: docs/repos/getCommit.md
+58-19
Original file line number
Diff line number
Diff line change
@@ -8,33 +8,72 @@ type: API method
8
8
9
9
# Get a commit
10
10
11
-
Returns the contents of a single commit reference. You must have `read` access for the repository to use this endpoint.
11
+
Returns the contents of a single commit reference. You must have `read` access for the repository to use this
12
+
endpoint.
12
13
13
-
You can pass the appropriate [media type](https://developer.github.com/v3/media/#commits-commit-comparison-and-pull-requests)to fetch `diff` and `patch` formats. Diffs with binary data will have no `patch` property.
14
+
**Note:** If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.
14
15
15
-
To return only the SHA-1 hash of the commit reference, you can provide the `sha` custom [media type](https://developer.github.com/v3/media/#commits-commit-comparison-and-pull-requests) in the `Accept` header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.
16
+
You can pass the appropriate [media type](https://developer.github.com/v3/media/#commits-commit-comparison-and-pull-requests) to
17
+
fetch `diff` and `patch` formats. Diffs with binary data will have no `patch` property.
18
+
19
+
To return only the SHA-1 hash of the commit reference, you can provide the `sha` custom [media
20
+
type](https://developer.github.com/v3/media/#commits-commit-comparison-and-pull-requests) in the `Accept` header. You can use
21
+
this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by
22
+
providing the local SHA-1 reference as the ETag.
16
23
17
24
**Signature verification object**
18
25
19
-
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:
26
+
The response will include a `verification` object that describes the result of verifying the commit's signature. The
27
+
following fields are included in the `verification` object:
20
28
21
29
These are the possible values for `reason` in the `verification` object:
|`expired_key`| The key that made the signature is expired. |
26
-
|`not_signing_key`| The "signing" flag is not among the usage flags in the GPG key that made the signature. |
27
-
|`gpgverify_error`| There was an error communicating with the signature verification service. |
28
-
|`gpgverify_unavailable`| The signature verification service is currently unavailable. |
29
-
|`unsigned`| The object does not include a signature. |
30
-
|`unknown_signature_type`| A non-PGP signature was found in the commit. |
31
-
|`no_user`| No user was associated with the `committer` email address in the commit. |
32
-
|`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. |
33
-
|`bad_email`| The `committer` email address in the commit is not included in the identities of the PGP key that made the signature. |
34
-
|`unknown_key`| The key that made the signature has not been registered with any user's account. |
35
-
|`malformed_signature`| There was an error parsing the signature. |
36
-
|`invalid`| The signature could not be cryptographically verified using the key whose key-id was found in the signature. |
37
-
|`valid`| None of the above errors applied, so the signature is considered to be verified. |
31
+
| Value |
32
+
Description
33
+
|
34
+
35
+
## | ------------------------ |
36
+
37
+
|
38
+
39
+
| `expired_key` | The key that made the signature is
40
+
expired. |
41
+
42
+
| `not_signing_key` | The "signing" flag is not among the usage flags in the GPG key that made the
43
+
signature. |
44
+
45
+
| `gpgverify_error` | There was an error communicating with the signature verification
46
+
service. |
47
+
48
+
| `gpgverify_unavailable` | The signature verification service is currently
49
+
unavailable. |
50
+
51
+
| `unsigned` | The object does not include a
52
+
signature. |
53
+
54
+
| `unknown_signature_type` | A non-PGP signature was found in the
55
+
commit. |
56
+
57
+
| `no_user` | No user was associated with the `committer` email address in the
58
+
commit. |
59
+
60
+
| `unverified_email` | The `committer` email address in the commit was associated with a user, but the email
61
+
address is not verified on her/his account. |
62
+
63
+
| `bad_email` | The `committer` email address in the commit is not included in the identities of the PGP
64
+
key that made the signature. |
65
+
66
+
| `unknown_key` | The key that made the signature has not been registered with any user's
67
+
account. |
68
+
69
+
| `malformed_signature` | There was an error parsing the
70
+
signature. |
71
+
72
+
| `invalid` | The signature could not be cryptographically verified using the key whose key-id was
73
+
found in the signature. |
74
+
75
+
| `valid` | None of the above errors applied, so the signature is considered to be
Specify a custom domain for the repository. Sending a `null` value will remove the custom domain. For more about custom domains, see "[Using a custom domain with GitHub Pages](https://docs.github.com/articles/using-a-custom-domain-with-github-pages/)."
38
43
39
44
</td></tr>
40
-
<tr><td>source</td><td>no</td><td>
45
+
<tr><td>source</td><td>yes</td><td>
46
+
47
+
Update the source for the repository. Must include the branch name and path.
48
+
49
+
</td></tr>
50
+
<tr><td>source.branch</td><td>yes</td><td>
51
+
52
+
The repository branch used to publish your site's source files.
53
+
54
+
</td></tr>
55
+
<tr><td>source.path</td><td>yes</td><td>
41
56
42
-
Update the source for the repository. Must include the branch name, and may optionally specify the subdirectory `/docs`. Possible values are `"gh-pages"`, `"master"`, and `"master /docs"`.
57
+
The repository directory that includes the source files for the Pages site. Allowed paths are `/` or `/docs`.
0 commit comments