> There's no amount of git competency that changes the fact that GitHub PRs operate at the branch level, not the commit level. Most all CI tools support per-co

> There's no amount of git competency that changes the fact that GitHub PRs operate at the branch level, not the commit level. Most all CI tools support per-commit checks with simple configuration/scripting of their execution DSL/API. In GitHub, push actions already works this way. You can do the same thing on any branch after a PR is opened: on synchronize you can iterate over all the updated refs, run checks, and publish results to the commit status API https://docs.github.com/en/rest/commits/statuses https://docs.github.com/en/rest/commits/statuses, and https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks https://docs.github.com/en/pull-requests/collaborating-with-....