@bchadwic Hey! We discussed this in a triage call & think that the existing categorization actually makes a bit more sense given that a "CANCELLED" workflow/action results in a failure for PRs. Going to close this for now unless you feel strongly otherwise & we can reopen discussion or try to find a nuanced way to display cancellations vs. failures.

@bchadwic I realize that our decision here kind of overrides the suggestion you got in #4090 (review), but we've thought this through and concluded that as long as "cancelled" counts as a failure on the platform, we're much more comfortable with it being rendered and reported as a failure rather than it being rendered and counted together with neutral statuses like "skipped".

Instead, would you be open to changing gh run so it renders cancelled status as "X"?

Instead, would you be open to changing gh run so it renders cancelled status as "X"?

Yeah, definitely! Making the checks uniform was my main concern, whether "cancelled" is "X" or "-" doesn't bother me a bit.

Out of curiosity though, what scenario does "cancelled" happen? Is it user driven or something on the backend?

Also, @darcyclarke, can we open this pr back up with the intent to change gh run instead now? Thank you.

Workflow runs may be cancelled via the API, via the web UI while a workflow is running, or by the Actions infrastructure itself (by default, one failed job in a matrix will auto-cancel all other running jobs in that matrix).