act workflow_dispatch inputs missing running Actions locally
On GitHub you supply workflow_dispatch inputs through the UI or API. act does not prompt for them, so inputs.* is empty unless you trigger the workflow_dispatch event and pass values with --input or an event JSON file.
What this error means
A step reads inputs.version (or similar) as empty and fails or uses a default, because no dispatch input was provided to act.
act
Error: Input 'version' is required but was empty
| inputs.version resolved to an empty stringCommon causes
The workflow_dispatch event was not triggered
Running act with the default push event never populates dispatch inputs at all.
No input values were supplied
Even on workflow_dispatch, act leaves inputs empty unless you pass --input or an event payload file.
How to fix it
Trigger dispatch with inputs
Run the workflow_dispatch event and pass each input value.
Terminal
act workflow_dispatch --input version=1.2.3 -j releaseProvide an event payload file
Supply a JSON payload with the inputs under inputs and pass it with -e.
Terminal
act workflow_dispatch -e event.jsonHow to prevent it
- Trigger the
workflow_dispatchevent explicitly with act. - Pass required inputs with
--inputor an event payload file. - Set sensible defaults so missing local inputs do not break the run.
Related guides
act job "skipped" because a needs dependency did not run locallyFix act jobs that are skipped - a job with needs: or an if: condition may not run under act when the upstream…
act matrix strategy runs differently running Actions locallyUnderstand act matrix behavior - act expands strategy.matrix but runs all combinations on the same container…
act "actions/cache" is a no-op running Actions locallyUnderstand act and actions/cache - the GitHub cache service does not exist locally, so actions/cache saves an…