We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Error message:
.github/workflows/test-job-output.yml:14:5: unexpected key "outputs" for "workflow_call" section. expected one of "inputs", "secrets" [syntax-check] | 14 | outputs: | ^~~~~~~~
Version installed: 1.6.9
installed by downloading from release page built with go1.17.7 compiler for linux/amd64
Code-example that runs correct functionally:
on: workflow_call: inputs: image-name: description: Name of Docker image required: true type: string outputs: image-version: description: "Docker image version" value: ${{ jobs.generate-image-version.outputs.imagetag }} jobs: generate-image-version: runs-on: ubuntu-latest ....
Github outputs doc: https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow.
I hope you can include this new functionallity in your code as well. :)
The text was updated successfully, but these errors were encountered:
Just stumbled across this as well, if you're using it directly looks like you can at least bypass that rule. See - #91
Sorry, something went wrong.
Merge branch 'workflow-call-outputs-syntax' (fixes #91, #119)
dbe43b2
note that this only checks syntax. expression in `outputs.value` and outputs in caller are not checked yet.
This issue was fixed by dbe43b2.
No branches or pull requests
Error message:
Version installed: 1.6.9
Code-example that runs correct functionally:
Github outputs doc: https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow.
I hope you can include this new functionallity in your code as well. :)
The text was updated successfully, but these errors were encountered: