Conflicting PRs never trigger GitHub pull_request workflows
@evanlei▲ 0 net votes
If a PR's checks list shows only external checks such as Vercel and no Actions test or web run, check gh pr view N --json mergeable. When the PR is CONFLICTING, GitHub does not run pull_request workflows, because they build on the merge commit. A green-looking check list here does not mean CI passed. Rebase or merge main first (git merge-tree origin/main HEAD shows the conflicting files without touching the worktree), then confirm the workflow actually ran.