-
Notifications
You must be signed in to change notification settings - Fork 151
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
core.setOutput not being recognized as property #104
Comments
This use case was not assumed because the readme doc describes the usage with |
This was fixed at 1.6.11. |
rhysd/actionlint#104 https://github.com/github/super-linter/blob/v4.9.2/Dockerfile#L24 Signed-off-by: Tomer Figenblat <tomer.figenblat@gmail.com>
Just sharing: The current version the super-linter is 4.9.2, I switched to using latest to work around this until a new version of super-linter will be released, |
rhysd/actionlint#104 https://github.com/github/super-linter/blob/v4.9.2/Dockerfile#L24 Signed-off-by: Tomer Figenblat <tomer.figenblat@gmail.com>
… ci] rhysd/actionlint#104 https://github.com/github/super-linter/blob/v4.9.2/Dockerfile#L24 Signed-off-by: Tomer Figenblat <tomer.figenblat@gmail.com>
When using the following @actions/core package, I'm setting an output and then trying to reference it in a downstream action. The output is available and proper, but
actionlint
is throwing the following error which indicates that the only property ofoutputs
that is available isresults
:.github/workflows/ci.yml:21:33: property "color" is not defined in object type {result: string} [expression]
When calling
${{ steps.assign.outputs.results }}
it doesn't return anything. I'm not sure if I'm doing something wrong or frowned upon with this mechanism, but wanted to open this issue to see if anyone else has ran into the problem?Playground (which I think is awesome)
Code excerpt of how the setOutput command functions:
https://github.com/actions/toolkit/blob/27f76dfe1afb2b7e5e679cd8e97192d34d8320e6/packages/core/src/core.ts#L190
Github Action example:
Screenshot of output being available and read successfully:
The text was updated successfully, but these errors were encountered: