A pull request with no checks: is it safe to merge to production?

No checks on a pull request does not mean the code was tested and passed. It means nothing reported a result. For tools that merge automatically, an empty list is easy to read as "all green", and that is a mistake.

Why a pull request can have none

What GitHub does about it

If a branch protection rule requires checks, GitHub blocks the merge until they report. If it does not, GitHub merges. A rule that requires no checks accepts a pull request with none.

What to do before merging to production

What Merge Scheduler does

When the pinned commit has no check runs and no commit statuses, Merge Scheduler says so in the timeline and in the email: "none found on this commit, so there was nothing to wait for". It then merges, because nothing is blocking it. It does not pretend that something passed. If you want checks to be mandatory, require them in branch protection. GitHub will block the merge and the release will be skipped with the reason.

Do this in Merge Scheduler: Schedule your first merge · Add a health check URL to catch bad releases that deploy green

Related: GitHub checks explained: check runs, commit statuses and required checks · CI/CD gates: checks before the merge and checks after the deploy · Releasing outside business hours: a checklist for small teams