workflow inputs
Named, typed values a person or a calling workflow supplies when starting a workflow, read through the inputs context.
In more detail
Inputs are declared under workflow_dispatch or workflow_call with a type such as string or choice and whether they are required. A step reads them as ${{ inputs.name }}, ideally passed through env.
Related terms
- workflow_dispatch — The workflow event that adds a Run workflow button so a person can start the workflow on purpose, optionally with typed inputs.
- reusable workflow — A workflow that declares the workflow_call event so another workflow can run it as a job, like calling a function.
- workflow context — A named object, such as steps, needs, matrix, secrets or runner, that expressions read to get facts about the current run.
Taught in
- Triggers and the Event Model — Continuous Integration & Continuous Delivery Pipelines
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Reusable Workflows: Inputs, Secrets And Outputs Across A Call — GitHub Actions (GH-200) Exam Prep
- action.yml: Inputs, Outputs, Runs And Branding — GitHub Actions (GH-200) Exam Prep
- Building And Debugging A JavaScript Action — GitHub Actions (GH-200) Exam Prep