GitHub Actions workflow run skipped due to a path filter

By Daniel Zoghalchali·Latchkey

When on: includes a paths or paths-ignore filter, a push or PR only triggers the workflow if changed files match. A too-strict filter silently skips runs you expected to fire.

What this error means

A push or PR that should run CI produces no workflow run (or a run marked skipped), because none of the changed files matched the configured paths filter.

on:
  push:
    paths:
      - 'src/**'   # a change only under docs/** triggers nothing

Common causes

paths filter too narrow

The changed files fall outside the paths patterns, so the event does not trigger the workflow.

paths-ignore excludes the change

A paths-ignore pattern matched the changed files and suppressed the run.

How to fix it

Widen or correct the path filters

1. Confirm the changed paths against the patterns.
2. Broaden paths or remove an over-eager paths-ignore.
3. For required checks, use a separate always-running job to report status.

on:
  push:
    paths:
      - 'src/**'
      - 'package*.json'
      - '.github/workflows/**'

How to prevent it

• Keep paths filters in sync with the real project layout.
• Account for required status checks that need a run on every push.
• Test path filters against representative changes.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions