Why a merged pull request didn't start your deploy workflow

You merged a pull request and your deploy workflow, which runs on push to main, never started. Or an automation merged it and nothing happened. A common cause is a deliberate GitHub rule.

The rule

According to GitHub's documentation, events triggered by the repository's GITHUB_TOKEN generally do not create new workflow runs. The exceptions are workflow_dispatch and repository_dispatch. This stops a workflow from triggering itself in a loop.

How it bites

The fixes

How to check which case you have

How Merge Scheduler behaves

Merge Scheduler merges with its own GitHub App identity, not your workflow's token, so your deploy workflow starts as if a person had pressed the button. It then looks for the runs triggered by that merge commit. If it finds none within the time you set, it tells you instead of assuming the deploy succeeded.

Do this in Merge Scheduler: Set up automatic revert for a failed deploy

Related: Why your auto-rollback job can't push the revert to main · How to schedule a GitHub pull request merge (4 ways) · GitHub auto-merge, merge queue and scheduled merge: what each is for