GitHub
Releases
Code quality
Stability
No CI workflows — no status checks to gate merges
Part of the Release & branch safety check · fix arrives as a guide
What it is
The repository has no CI workflows, so branch protection has no status checks it could require before a merge.
Why it matters
Nothing mechanical stands between a pull request and the default branch. Correctness depends entirely on the reviewer noticing, on every change, which is not a control that holds up over time.
How to fix it
Add a workflow running install, typecheck, lint, and tests on pull requests, then require it in branch protection. Even a build-only check catches a meaningful share of breakage.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.