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/checks/createSuite.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.
4
4
5
-
By default, check suites are automatically created when you create a [check run](https://developer.github.com/v3/checks/runs/). You only need to use this endpoint for manually creating check suites when you've disabled automatic creation using "[Set preferences for check suites on a repository](https://developer.github.com/v3/checks/suites/#set-preferences-for-check-suites-on-a-repository)". Your GitHub App must have the `checks:write` permission to create check suites.
5
+
By default, check suites are automatically created when you create a [check run](https://developer.github.com/v3/checks/runs/). You only need to use this endpoint for manually creating check suites when you've disabled automatic creation using "[Update repository preferences for check suites](https://developer.github.com/v3/checks/suites/#update-repository-preferences-for-check-suites)". Your GitHub App must have the `checks:write` permission to create check suites.
Copy file name to clipboardExpand all lines: docs/checks/get.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Get a single check run
1
+
# Get a check run
2
2
3
3
**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array.
4
4
@@ -41,4 +41,4 @@ check_run_id parameter
41
41
</tbody>
42
42
</table>
43
43
44
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/runs/#get-a-single-check-run).
44
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/runs/#get-a-check-run).
Copy file name to clipboardExpand all lines: docs/checks/getSuite.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Get a single check suite
1
+
# Get a check suite
2
2
3
3
**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.
4
4
@@ -41,4 +41,4 @@ check_suite_id parameter
41
41
</tbody>
42
42
</table>
43
43
44
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#get-a-single-check-suite).
44
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#get-a-check-suite).
Copy file name to clipboardExpand all lines: docs/checks/listAnnotations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# List annotations for a check run
1
+
# List check run annotations
2
2
3
3
Lists annotations for a check run using the annotation `id`. GitHub Apps must have the `checks:read` permission on a private repository or pull access to a public repository to get annotations for a check run. OAuth Apps and authenticated users must have the `repo` scope to get annotations for a check run in a private repository.
4
4
@@ -49,4 +49,4 @@ Page number of the results to fetch.
49
49
</tbody>
50
50
</table>
51
51
52
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/runs/#list-annotations-for-a-check-run).
52
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/runs/#list-check-run-annotations).
Copy file name to clipboardExpand all lines: docs/checks/listForRef.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# List check runs for a specific ref
1
+
# List check runs for a Git reference
2
2
3
3
**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array.
4
4
@@ -66,4 +66,4 @@ Page number of the results to fetch.
66
66
</tbody>
67
67
</table>
68
68
69
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/runs/#list-check-runs-for-a-specific-ref).
69
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/runs/#list-check-runs-for-a-git-reference).
Copy file name to clipboardExpand all lines: docs/checks/listSuitesForRef.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# List check suites for a specific ref
1
+
# List check suites for a Git reference
2
2
3
3
**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.
4
4
@@ -61,4 +61,4 @@ Page number of the results to fetch.
61
61
</tbody>
62
62
</table>
63
63
64
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#list-check-suites-for-a-specific-ref).
64
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#list-check-suites-for-a-git-reference).
Copy file name to clipboardExpand all lines: docs/checks/rerequestSuite.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Rerequest check suite
1
+
# Rerequest a check suite
2
2
3
3
Triggers GitHub to rerequest an existing check suite, without pushing new code to a repository. This endpoint will trigger the [`check_suite` webhook](https://developer.github.com/v3/activity/events/types/#checksuiteevent) event with the action `rerequested`. When a check suite is `rerequested`, its `status` is reset to `queued` and the `conclusion` is cleared.
4
4
@@ -41,4 +41,4 @@ check_suite_id parameter
41
41
</tbody>
42
42
</table>
43
43
44
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#rerequest-check-suite).
44
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#rerequest-a-check-suite).
Copy file name to clipboardExpand all lines: docs/checks/setSuitesPreferences.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Set preferences for check suites on a repository
1
+
# Update repository preferences for check suites
2
2
3
3
Changes the default automatic flow when creating check suites. By default, the CheckSuiteEvent is automatically created each time code is pushed to a repository. When you disable the automatic creation of check suites, you can manually [Create a check suite](https://developer.github.com/v3/checks/suites/#create-a-check-suite). You must have admin permissions in the repository to set preferences for check suites.
4
4
@@ -50,4 +50,4 @@ Set to `true` to enable automatic creation of CheckSuite events upon pushes to t
50
50
</tbody>
51
51
</table>
52
52
53
-
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#set-preferences-for-check-suites-on-a-repository).
53
+
See also: [GitHub Developer Guide documentation](https://developer.github.com/v3/checks/suites/#update-repository-preferences-for-check-suites).
"description": "**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array.\n\nGets a single check run using its `id`. GitHub Apps must have the `checks:read` permission on a private repository or pull access to a public repository to get check runs. OAuth Apps and authenticated users must have the `repo` scope to get check runs in a private repository.",
"description": "Lists annotations for a check run using the annotation `id`. GitHub Apps must have the `checks:read` permission on a private repository or pull access to a public repository to get annotations for a check run. OAuth Apps and authenticated users must have the `repo` scope to get annotations for a check run in a private repository.",
"description": "**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.\n\nBy default, check suites are automatically created when you create a [check run](https://developer.github.com/v3/checks/runs/). You only need to use this endpoint for manually creating check suites when you've disabled automatic creation using \"[Set preferences for check suites on a repository](https://developer.github.com/v3/checks/suites/#set-preferences-for-check-suites-on-a-repository)\". Your GitHub App must have the `checks:write` permission to create check suites.",
18571
+
"description": "**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.\n\nBy default, check suites are automatically created when you create a [check run](https://developer.github.com/v3/checks/runs/). You only need to use this endpoint for manually creating check suites when you've disabled automatic creation using \"[Update repository preferences for check suites](https://developer.github.com/v3/checks/suites/#update-repository-preferences-for-check-suites)\". Your GitHub App must have the `checks:write` permission to create check suites.",
"description": "Changes the default automatic flow when creating check suites. By default, the CheckSuiteEvent is automatically created each time code is pushed to a repository. When you disable the automatic creation of check suites, you can manually [Create a check suite](https://developer.github.com/v3/checks/suites/#create-a-check-suite). You must have admin permissions in the repository to set preferences for check suites.",
"description": "**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.\n\nGets a single check suite using its `id`. GitHub Apps must have the `checks:read` permission on a private repository or pull access to a public repository to get check suites. OAuth Apps and authenticated users must have the `repo` scope to get check suites in a private repository.",
"description": "Triggers GitHub to rerequest an existing check suite, without pushing new code to a repository. This endpoint will trigger the [`check_suite` webhook](https://developer.github.com/v3/activity/events/types/#checksuiteevent) event with the action `rerequested`. When a check suite is `rerequested`, its `status` is reset to `queued` and the `conclusion` is cleared.\n\nTo rerequest a check suite, your GitHub App must have the `checks:read` permission on a private repository or pull access to a public repository.",
"description": "**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array.\n\nLists check runs for a commit ref. The `ref` can be a SHA, branch name, or a tag name. GitHub Apps must have the `checks:read` permission on a private repository or pull access to a public repository to get check runs. OAuth Apps and authenticated users must have the `repo` scope to get check runs in a private repository.",
"description": "**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.\n\nLists check suites for a commit `ref`. The `ref` can be a SHA, branch name, or a tag name. GitHub Apps must have the `checks:read` permission on a private repository or pull access to a public repository to list check suites. OAuth Apps and authenticated users must have the `repo` scope to get check suites in a private repository.",
Copy file name to clipboardExpand all lines: src/generated/types.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -28988,7 +28988,7 @@ export type RestEndpointMethods = {
28988
28988
/**
28989
28989
* **Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.
28990
28990
*
28991
-
* By default, check suites are automatically created when you create a [check run](https://developer.github.com/v3/checks/runs/). You only need to use this endpoint for manually creating check suites when you've disabled automatic creation using "[Set preferences for check suites on a repository](https://developer.github.com/v3/checks/suites/#set-preferences-for-check-suites-on-a-repository)". Your GitHub App must have the `checks:write` permission to create check suites.
28991
+
* By default, check suites are automatically created when you create a [check run](https://developer.github.com/v3/checks/runs/). You only need to use this endpoint for manually creating check suites when you've disabled automatic creation using "[Update repository preferences for check suites](https://developer.github.com/v3/checks/suites/#update-repository-preferences-for-check-suites)". Your GitHub App must have the `checks:write` permission to create check suites.
0 commit comments