in the first place, thanks for building this lovely thingy :>
i tried to use it for my own repos, but there were no results. apparently github actions/workflows use a different thing from commit statuses, called checks shrug.
it seems the graphql api is the only api providing a combined status field for both of these (statusCheckRollup).
using graphql also saves a few requests. it allows querying the default ref directly, for instance.
the commit also adds a status icon to individual checks, so one can directly see which of the builds/test runs/checkers failed.
note: i have tested all combinations (repos with only classical status, repos with classical status and checks, repos with only checks, repos with nothing), but have tested NO throttling, retry, or network error cases.
jaynetics
commented
3 years ago 
in the first place, thanks for building this lovely thingy :>
i tried to use it for my own repos, but there were no results. apparently github actions/workflows use a different thing from commit statuses, called checks shrug.
it seems the graphql api is the only api providing a combined status field for both of these (statusCheckRollup).
using graphql also saves a few requests. it allows querying the default ref directly, for instance.
the commit also adds a status icon to individual checks, so one can directly see which of the builds/test runs/checkers failed.
note: i have tested all combinations (repos with only classical status, repos with classical status and checks, repos with only checks, repos with nothing), but have tested NO throttling, retry, or network error cases.