Every pull request, checked.

Turn it on for a GitHub repository, and each push to a pull request gets a SlopCop check, with every new finding on the line that raised it.

How it works

Turned on per repository: A workspace owner or manager turns on Check pull requests in the repository’s settings. The SlopCop GitHub App asks once for permission to post checks, and nobody signs in again.
On every push: When a pull request is opened or pushed to, SlopCop checks what it changes since it branched: the same change and the same rules as slopcop check on its head.
On the lines it changed: Each new finding appears in Files changed on the line that raised it, with the rule, its severity and the file. Findings already in the code are counted, and never fail the check.
Before it merges: Make SlopCop a required check in branch protection, and a pull request with new findings can’t merge until they’re fixed. Re-run it from the pull request at any time.

Never a false all-clear: A rule that can’t finish leaves the check neutral, never green, and the check says which rules didn’t finish.
Pull requests from forks: A fork’s pull request is checked when its author is an owner, member or collaborator of the repository. Anyone else’s gets a check that says it wasn’t checked.
Checks are free: On a pull request as in your agent’s loop. A workspace pays for each active repository after its first, whichever way it’s checked.