GitHub Actions dorny/paths-filter "predicate-quantifier" error
dorny/paths-filter supports predicate-quantifier (some or every) to control how multiple patterns in a filter combine. An invalid value, or using every without understanding it requires all patterns to match, produces unexpected or failing evaluation.
What this error means
A paths-filter step errors on the predicate-quantifier input, or filters evaluate to false unexpectedly when every is set.
github-actions
Error: Input parameter 'predicate-quantifier' must be one of: 'some', 'every'Common causes
Invalid predicate-quantifier value
Only some (default) and every are accepted; anything else errors.
every semantics misunderstood
With every, a changed file must match all patterns in the filter, which often yields no matches.
How to fix it
Use a valid quantifier and correct filter shape
- Set predicate-quantifier to some or every only.
- Use some (default) when any matching pattern should activate the filter.
- Reserve every for include-and-exclude pattern combinations.
.github/workflows/ci.yml
- uses: dorny/paths-filter@v3
with:
predicate-quantifier: 'some'
filters: |
src:
- 'src/**'How to prevent it
- Default to some unless you specifically need all-pattern matching.
- Test filter behavior on a representative changeset.
Related guides
GitHub Actions tj-actions/changed-files "fatal: ambiguous argument"Fix tj-actions/changed-files "fatal: ambiguous argument" - a shallow checkout lacks the history needed to dif…
actions/labeler: Auto-Label PRs by Changed PathsReference for actions/labeler: automatically apply labels to pull requests based on which files they touch, c…
GitHub Actions actions/github-script "require is not defined" (ESM)Fix actions/github-script "ReferenceError: require is not defined" - ESM-style imports or top-level await wer…