Closed webknjaz closed 10 months ago
Yep; accepted! The schema was written with type: number
. I'll put something in for expression evaluation strings and then it can be OR-ed together.
This is where I'm trying to stick it, by the way: https://github.com/aio-libs/yarl/blob/3a5e605/.github/workflows/reusable-build-wheel.yml#L38.
I just got around to this today and handled it in v0.27.2, freshly released! Please let me know if it does or doesn't work for you.
@sirosen yes, thank you! Just got to verifying and it does work for me: https://github.com/aio-libs/frozenlist/commit/a1c0e492308c3f76dff72a442e806f08a11312c9 / https://github.com/aio-libs/frozenlist/commit/3367693497276766c03d5f53ac6b344a1cf93ed9.
Though, there was one problem with my example above: the numbers should be unquoted. So it must be timeout-minutes: ${{ inputs.qemu && 60 || 20 }}
. I don't know why I thought the quoted values worked — perhaps, it does work in non-reusable workflows or something changed.
Anyway, the schema looks good to me now.
$sbj. I want to have
timeout-minutes: ${{ inputs.qemu && '60' || '20' }}
set for a job. Theinputs
is a context that exists in reusable workflows. Here's the table of context availability FTR: https://docs.github.com/en/actions/learn-github-actions/contexts.Here's how it fails for me:
Approximate reusable workflow look:
Haven't looked into how to fix this, but the upstream
github-workflow.json
doesn't error out, so this custom schema must be too strict...