Source code
Code quality
Releases
No CI gates on main
Part of the Production readiness check · fix arrives as a guide
What it is
The default branch has no required status checks, so a pull request can merge without CI having passed.
Why it matters
Tests that do not block a merge are advisory. It only takes one urgent merge over a red build for the habit to set in, and after that the pipeline reports on main rather than protecting it.
How to fix it
Require the CI checks on the default branch in your host's branch protection settings, and require the branch to be up to date so a merge cannot combine two individually-green changes into a broken one.
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.