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.
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
Github workflow parameter types too narrow #1819
Comments
Action inputs are strings. Numbers and booleans are allowed for convenience when writing yaml, but they get converted to strings too. In this case, |
The github action expects an array, not a string containing brackets. Of course this would solve the schemastore issue since the type would become string, but the api call would fail since it doesn't expect a string. |
Structured input (maps and lists) cannot be passed to an action as an input value unless it is represented as a string. That's a limitation of the GitHub Actions runner, and the schema in SchemaStore simply reflects that behavior. It is the responsibility of |
Description of the JSON schema.
required_contexts
should allow[]
such as:required_contexts: []
Supporting information.
The text was updated successfully, but these errors were encountered: