Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: Unexpected input(s) 'predicate-quantifier' #225

Open
petermetz opened this issue Mar 4, 2024 · 2 comments · May be fixed by #226
Open

fix: Unexpected input(s) 'predicate-quantifier' #225

petermetz opened this issue Mar 4, 2024 · 2 comments · May be fixed by #226

Comments

@petermetz
Copy link
Contributor

The Problem

The error message shown when I try to use the new predicate quantifier feature is pasted below.
The feature was introduced by: #224

Unexpected input(s) 'predicate-quantifier', valid inputs are ['token', 'working-directory', 'ref', 'base', 'filters', 'list-files', 'initial-fetch-depth']

Root Cause Analysis

The pull request added the feature in the code but did not declare the predicate-quantifier parameter as a possible input in the action.yml file which is standard for GitHub actions.
petermetz added a commit to petermetz/paths-filter that referenced this issue Mar 4, 2024
@petermetz
fix: Unexpected input(s) 'predicate-quantifier'
5ee2f5d 
Declared the input parameter in the action.yml file so GitHub should
no longer complain about invalid input when we use the new feature.

Fixes dorny#225

Signed-off-by: Peter Somogyvari <[email protected]>
@petermetz petermetz linked a pull request Mar 4, 2024 that will close this issue
Open
@hintron hintron mentioned this issue Aug 28, 2024
Open
sekiye pushed a commit to alpaca-engineer/paths-filter that referenced this issue Dec 10, 2024
@petermetz @sekiye
fix: Unexpected input(s) 'predicate-quantifier'
f8f61cd 
Declared the input parameter in the action.yml file so GitHub should
no longer complain about invalid input when we use the new feature.

Fixes dorny#225

Signed-off-by: Peter Somogyvari <[email protected]>
@sumanmaity112
Copy link

Any update on this issue?

@dswaffordcw dswaffordcw mentioned this issue Feb 1, 2025
Closed
dswaffordcw added a commit to dswaffordcw/paths-filter that referenced this issue Feb 1, 2025
@dswaffordcw
fix: warning for "unexpected input predicate-quantifier"
4c1c3ac 
Fixes dorny#225

Signed-off-by: David Swafford <[email protected]>
@valy-catches
Copy link

As far as I can tell, the feature itself works, so the warning can be ignored.

@bhansconnect bhansconnect mentioned this issue Feb 8, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Unexpected input(s) 'predicate-quantifier' petermetz/paths-filter
3 participants
@petermetz @sumanmaity112 @valy-catches