Mobster. It works wherever Mobster runs the checks: mobster test pr on your Mac, a coding agent’s test_pr, and mobster ci or the Mobster test action on your runner.
The check holds what passed, what failed, what each check expected and found, and the command that runs a failure again. You can also have Mobster keep one comment on the pull request.
Set it up
- Install Mobster Checks on your repositories: github.com/apps/mobster-checks. In Mobster, the GitHub checks card under Send results to in Connectors opens the same page.
- In Mobster, connect GitHub (Connectors). Mobster uses that sign-in to confirm you can push to the repository.
- Keep Mobster open, signed in, with your plan or free trial.
Mobster as in progress while the checks run, then the verdict.
The check
Its summary is the pull request comment: a row per check with what it expected and found, and a repro for each failure. In CI, each frame, GIF and video links to the job’s report. On your Mac, they stay in
.mobster/test-results/ and the summary names them.
To block merging on a failure, add Mobster as a required check in the branch’s protection rules.
Keep one comment
--github comment also keeps one comment on the pull request, updated in place on every run:
--github off posts nothing. A coding agent passes the same choice to run_tests with pr as github. In a GitHub Actions job, the workflow’s own step keeps the comment (CI), so Mobster Checks posts only the check there.
When nothing is posted
Mobster says why in one line, and the verdict stays on your Mac:
A repository that isn’t on github.com posts nothing and says nothing.
What it can do
Mobster Checks asks GitHub for three permissions: checks (read and write), pull requests (read and write, for the comment) and metadata (read). It reads no code and has no webhook, so it never starts a run by itself. Its private key stays on Mobster’s server,api.mobster.dev. Each time Mobster posts, the server checks that your Mobster account has a plan or trial in force and that your GitHub sign-in can push to the repository. Then it gives your Mac a token for that one repository, good for an hour, which writes only checks and pull request comments. Your Mac posts to GitHub with it. The server keeps no token, and your GitHub sign-in stays in your Mac’s Keychain.
The first time mobster test pr or the test_pr tool posts to a repository while Mobster is open, Mobster asks you on a card: Let Mobster Checks post on GitHub? It asks once per repository until Mobster quits. Without your answer within 25 seconds, nothing is posted. So another program on your Mac that reads Mobster’s API token can’t get a GitHub token without you seeing it.