- pull_request is more dynamic in its life-cycle than check_suite as subsequent git pushes are made - ∴ the PR's latest head_sha may not match the check_suite's head_sha Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Grace Park <gracepark@github.com>
2.6 KiB
2.6 KiB
| Key | Type | Description |
|---|---|---|
action |
string |
The action performed. Can be one of:
|
check_run |
object |
The check_run. |
check_run[status] |
string |
The current status of the check run. Can be queued, in_progress, or completed. |
check_run[conclusion] |
string |
The result of the completed check run. Can be one of success, failure, neutral, cancelled, timed_out, {% ifversion fpt or ghes or ghae or ghec %}action_required or stale{% else %}or action_required{% endif %}. This value will be null until the check run has completed. |
check_run[name] |
string |
The name of the check run. |
check_run[check_suite][id] |
integer |
The id of the check suite that this check run is part of. |
check_run[check_suite][pull_requests] |
array |
An array of pull requests that match this check suite. A pull request matches a check suite if they have the same head_branch.Note:
|
check_run[check_suite][deployment] |
object |
A deployment to a repository environment. This will only be populated if the check run was created by a {% data variables.product.prodname_actions %} workflow job that references an environment. |
requested_action |
object |
The action requested by the user. |
requested_action[identifier] |
string |
The integrator reference of the action requested by the user. |