403 Resource not accessible by integration: the GitHub App permission that hid our CI results
No warning: GitHub's 403 can hide your private CI. 3 of ours. This is about a bug in Versyka, found on our own repositories. The symptom Four pull requests in three private repositories showed "CI not checked
No warning: GitHub's 403 can hide your private CI. 3 of ours. This is about a bug in Versyka, found on our own repositories.
The symptom
Four pull requests in three private repositories showed "CI not checked yet" in our dashboard. For days. Their CI had run and passed on GitHub. Versyka just never saw the result.
The cause
Every time the app asked GitHub for those pull requests' check runs, GitHub answered:
403 Resource not accessible by integration
On a public repository, any GitHub App can read check runs. On a private one, the app has to request the Checks permission (and Commit statuses for older status-based CI). Our app didn't.
So for every customer with private repositories:
- no CI state in the dashboard,
- auto-merge for version bumps never merged anything,
- "Merge all that passed CI" never listed those pull requests,
and nothing told anyone why. The error went to a log, not to a person.
Why we didn't catch it earlier
Our tests and demos ran against public repositories, where everything worked. The failure only exists when three things line up: a private repo, a GitHub App, and an endpoint that's open on public repos.
What we changed
- The app now requests Checks: read-only and Commit statuses: read-only. Each installed account gets GitHub's "review new permissions" prompt to accept.
- When the dashboard can't read CI for a repository, it says so, names the repositories and links straight to the permission.
If you build on GitHub Apps
- Test every feature on a private repository, not only a public one.
-
Treat
Resource not accessible by integrationas a missing permission, not a transient error. Retrying won't help. - Show permission errors to the user with the fix, instead of logging them.
What's the quietest bug you've found in your own product?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.