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

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 #225

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
This commit is contained in:
Peter Somogyvari 2024-03-03 22:27:46 -08:00
parent de90cc6fb3
commit 5ee2f5d4cf
No known key found for this signature in database
GPG key ID: 444FB843147AD5EB

View file

@ -44,6 +44,16 @@ inputs:
This option takes effect only when changes are detected using git against different base branch.
required: false
default: '100'
predicate-quantifier:
description: |
Makes the pattern evaluation customizable when it comes to matching files:
'every'- When choosing 'every' in the config it means that files will only get matched if all the
patterns are satisfied by the path of the file, not just at least one of them.
'some' - When choosing 'some' in the config it means that files will get matched as long as there is
at least one pattern that matches them. This is the default behavior if you don't
specify anything as a predicate quantifier. (default)
required: false
default: some
outputs:
changes:
description: JSON array with names of all filters matching any of changed files