Description
The check-run schema (used for REST API responses, e.g. GET /repos/{owner}/{repo}/check-runs/{check_run_id}) lists status as one of:
queued, in_progress, completed, waiting, requested, pending
But the check-run-with-simple-check-suite schema — used for the check_run webhook payload (components.schemas.check-run-with-simple-check-suite.properties.status) — only lists:
queued, in_progress, completed, pending
In practice, GitHub emits check_run webhook deliveries with status: "waiting" (and presumably "requested", matching the REST schema). Clients that generate strict enums from the webhook schema (e.g. OpenAPI codegen tools) fail to deserialize these real payloads with an "unrecognized enum value" error.
Expected
check-run-with-simple-check-suite.status should list the same enum values as check-run.status: queued, in_progress, completed, waiting, requested, pending.
Description
The
check-runschema (used for REST API responses, e.g.GET /repos/{owner}/{repo}/check-runs/{check_run_id}) listsstatusas one of:But the
check-run-with-simple-check-suiteschema — used for thecheck_runwebhook payload (components.schemas.check-run-with-simple-check-suite.properties.status) — only lists:In practice, GitHub emits
check_runwebhook deliveries withstatus: "waiting"(and presumably"requested", matching the REST schema). Clients that generate strict enums from the webhook schema (e.g. OpenAPI codegen tools) fail to deserialize these real payloads with an "unrecognized enum value" error.Expected
check-run-with-simple-check-suite.statusshould list the same enum values ascheck-run.status:queued, in_progress, completed, waiting, requested, pending.