-
Hi, So I have this workflow that gathers the version from a website and then triggers a build (another workflow), via the workflow_call trigger. This is the code of the scheduler:
The problem is that the version variable is being set as empty string. I have tried using a step in the last job and it works, its just when I use the
Any fix for this issue? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
Afaict, from:
Can you provide a sample repository? |
Beta Was this translation helpful? Give feedback.
-
Sure! Here it is. If you check the job trigger, the output is not propagated, but it works on job tst. |
Beta Was this translation helpful? Give feedback.
-
Personally, I’d want to fix this:
Checks for new releases and deploys master ·...Contribute to afonsoc12/docker-cloudflared development by creating an account on GitHub. I’d probably add a I’d probably also enable debug logging: |
Beta Was this translation helpful? Give feedback.
-
Thanks, sure the scripts are still very crude, I am looking forward to fix CI first. |
Beta Was this translation helpful? Give feedback.
-
https://github.com/check-spelling/docker-cloudflared/runs/6478217149?check_suite_focus=true#step:3:1 |
Beta Was this translation helpful? Give feedback.
-
I should probably explain, but in short: A slightly longer explanation is certainly in order. Literally, the google completion for GitHub supports events that have inputs: It also supports giving (reusable) workflows inputs: In that case, inputs come via Note that this aligns with actions: |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
This problem still persists.
with seems like OP's solution was to just paste the |
Beta Was this translation helpful? Give feedback.
-
I am still facing the similar issue. |
Beta Was this translation helpful? Give feedback.
I should probably explain, but in short:
afonsoc12/docker-cloudflared@ee01e19
A slightly longer explanation is certainly in order.
Literally, the google completion for
github.event.inputs
isgithub.event.inputs vs inputs
.GitHub supports events that have inputs:
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#providing-inputs
It handles that via
github.event.inputs
It also supports giving (reusable) workflows inputs:
https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow
In that case, inputs come via
inputs
Note that this aligns with actions:
https://docs.github.com/en/actions/creating-actions/…