Create a check suite
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
.
By default, check suites are automatically created when you create a check run. 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”. Your GitHub App must have the checks:write
permission to create check suites.
Path Parameters
Body
application/json
Body
The sha of the head commit.
Response
application/json
Response
when the suite already existed
CheckSuite
A suite of checks performed on the code of a given code change
Example:5
Example:MDEwOkNoZWNrU3VpdGU1
Example:master
The SHA of the head commit that is being checked.
Example:009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d
Allowed values:queuedin_progresscompleted
Example:completed
Allowed values:successfailureneutralcancelledskippedtimed_outaction_required
Example:neutral
Example:https://api.github.com/repos/github/hello-world/check-suites/5
Example:146e867f55c26428e5f9fade55a9bbf5e95a7912
Example:d6fde92930d4715a2b49857d24b940956b26d2d3
Show Child Parameters
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
Show Child Parameters
Minimal Repository
Show Child Parameters
Simple Commit
Show Child Parameters
Path Parameters
Body
Update repository preferences for check suites
Changes the default automatic flow when creating check suites. By default, a check suite 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. You must have admin permissions in the repository to set preferences for check suites.
Path Parameters
Body
application/json
Body
Enables or disables automatic creation of CheckSuite events upon pushes to the repository. Enabled by default. See the auto_trigger_checks
object description for details.
Show Child Parameters
Response
200 application/json
Response
Response
Check Suite Preference
Check suite configuration preferences for a repository.
Show Child Parameters
Minimal Repository
Show Child Parameters
Path Parameters
Body
Get a check suite
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
.
Gets 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.
Path Parameters
check_suite_id parameter
Response
200 application/json
Response
Response
CheckSuite
A suite of checks performed on the code of a given code change
Example:5
Example:MDEwOkNoZWNrU3VpdGU1
Example:master
The SHA of the head commit that is being checked.
Example:009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d
Allowed values:queuedin_progresscompleted
Example:completed
Allowed values:successfailureneutralcancelledskippedtimed_outaction_required
Example:neutral
Example:https://api.github.com/repos/github/hello-world/check-suites/5
Example:146e867f55c26428e5f9fade55a9bbf5e95a7912
Example:d6fde92930d4715a2b49857d24b940956b26d2d3
Show Child Parameters
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
Show Child Parameters
Minimal Repository
Show Child Parameters
Simple Commit
Show Child Parameters
Path Parameters
List check runs in a check suite
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.
Lists check runs for a 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 runs. OAuth Apps and authenticated users must have the repo
scope to get check runs in a private repository.
Query Parameters
Returns check runs with the specified name
.
Returns check runs with the specified status
. Can be one of queued
, in_progress
, or completed
.
Allowed values:queuedin_progresscompleted
Filters check runs by their completed_at
timestamp. Can be one of latest
(returning the most recent check runs) or all
.
Allowed values:latestall
Default:latest
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Path Parameters
check_suite_id parameter
Response
200 application/json
Response
Response
A check performed on the code of a given code change
Show Child Parameters
Path Parameters
Query Parameters
Rerequest a check suite
Triggers GitHub to rerequest an existing check suite, without pushing new code to a repository. This endpoint will trigger the check_suite
webhook event with the action rerequested
. When a check suite is rerequested
, its status
is reset to queued
and the conclusion
is cleared.
To rerequest a check suite, your GitHub App must have the checks:read
permission on a private repository or pull access to a public repository.
Path Parameters
check_suite_id parameter
Response
201 application/json
Response
Response