fix: warning for "unexpected input predicate-quantifier" #258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR addresses the GitHub warning:
Which appears in any GitHub action run using
dorny/paths-filter@v3
withpredicate-quantifier
configured.Description
At first, I thought my team's use of
dorny/paths-filter
was configured wrong. I thought I needed to remove our use ofpredicate-quantifier
but then saw this GitHub issue. That linked to the original PR where this was added.I am not familiar with GitHub action development, but upon browsing
action.yaml
, I see all of the other possible inputs defined. That did not havepredicate-quantifier
, so I believe this fix is as simple as defining it there. This PR adds that, with a description based on the comments added by the original author.Testing
I am unsure of how to test this change. Please advise and/or help with that aspect.