When I look at a pull request, I do not really care that a job named test is green. I care that the right tests ran, on the right commit, under a policy the pull request could not quietly weaken.
The green badge is still useful. It compresses a lot of work into one bit: pass or fail. Trouble starts when that bit becomes the whole argument for merging.
GitHub can associate a check run with a commit SHA, and branch protection can require a check from a selected GitHub App. But GitHub also documents an important boundary: required status checks are selected by name and do not take the workflow, matrix, or event type into account. A check name is therefore a useful merge control, not a complete answer to four separate questions:
Which exact candidate produced this result?
Which workflow and concrete job produced it?
