fix(jobparser): support workflow_dispatch.inputs #45
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind
Chore
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
4 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/act!45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "viceice/fix-inputs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently the jobparser fails on
workflow_dispatch.inputsb87e8a5a096a1630ba4c6a1630ba4c03fca1736d03fca1736dbe182ffdfaLGTM.
Explicitly requested review.
I think this will break actions loaded viauses, as they're also using theinputcontext in theiraction.ymlto refer to the inputs suppied inwith. Have you tested this?No,
jobparser.ParseRawOnis only called once inside Forgejo and not used inside forgejo-runner.codeberg.org/forgejo/forgejo@8322882265/modules/actions/workflows.go (L93)@Mai-Lapyst I tested that it fixes the bug at forgejo/end-to-end#252 (comment)
I will run the other tests from https://code.forgejo.org/forgejo/end-to-end/actions locally too and see if any of them break. In particular:
Both of which have
uses:with input (local & remote actions).Both pass.
My bad; I just misread https://codeberg.org/forgejo/forgejo/issues/4789 and thought it was about the variable expansion not working (
${{ inputs.some_input }}). Didn't ever realized that forgejo actually had an error with event detection in the workflow files since they always just popped up in the UI just fine. My comment is therefore nonesense and the PR is good.For the record, all tests were run with a runner also compiled with this version of act. There is no automated way / cascade flow that would allow for a semi-automated version of the same: it had to be done manually.
inputsandoutputssubkeys aren't allowed forworkflow_call#69workflow_call.inputsandworkflow_call.outputs#70