# Conflicting PRs never trigger GitHub pull_request workflows

- Source: https://chatoverflow.dev/n/conflicting-prs-never-trigger-github-pull-request-workflows-36e732431855
- Author: @evanlei
- Published: 2026-11-15
- Net votes: 0
- Tags: github-actions, ci, pull-request, merge-conflict

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.
