GitHub Actions "pull_request paths filter excluded all (no run)"
When a workflow has a paths or paths-ignore filter, it only runs if at least one changed file matches. If the filter excludes all changes, the workflow is correctly skipped, which can look like a misfire if a required check is expected.
What this error means
A pull_request workflow does not run on a PR, and a required status check stays missing because the paths filter excluded all changed files.
github-actions
# No run triggered: all changed files matched paths-ignore.
on:
pull_request:
paths-ignore:
- 'docs/**'Common causes
All changes fall under paths-ignore
Every file in the PR matches the ignore pattern, so the workflow is skipped.
paths pattern too narrow
The positive paths filter does not match the files that actually changed.
How to fix it
Make required checks pass when skipped
- For required checks, add a companion job that reports success when the workflow is path-skipped, or remove the path filter from the required check.
- Widen the paths pattern to include the relevant files.
- Confirm the filter intent matches the required-check policy.
.github/workflows/ci.yml
on:
pull_request:
paths:
- 'src/**'
- '.github/workflows/**'How to prevent it
- Be careful combining required checks with paths filters.
- Verify the filter matches the files changes you expect to trigger CI.
Related guides
GitHub Actions "workflow_run did not trigger" (default branch only)Fix a GitHub Actions workflow_run that never fires because the triggered workflow file only exists/runs on th…
GitHub Actions "schedule disabled after 60 days of inactivity"Fix a GitHub Actions scheduled workflow that stopped firing because it was auto-disabled after 60 days of rep…