A reusable workflow defines on.workflow_call.inputs.release_type as a string choice among patch, minor, and major for callers. How should callers pass the value?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Reusable workflow inputs are passed with: on the job that uses: the workflow file—same mental model as action inputs. Not repository_dispatch-only, runner labels, or CODEOWNERS.
Full explanation below image
Full Explanation
Callable workflows declare inputs under on.workflow_call.inputs with type, description, default, and required. Caller workflows invoke them with jobs.<id>.uses pointing at the workflow YAML ref and pass values under with: using the input names. Inside the reusable workflow, read inputs.release_type via the inputs context. repository_dispatch is a different trigger for external automation and is not required for workflow_call. Runner group labels select execution hosts; they do not carry workflow inputs. CODEOWNERS controls review assignment. For secrets, use secrets: inherit or explicitly map secrets: under the caller job—do not stuff secrets into string inputs. Choice-like behavior is typically enforced by documentation and caller discipline or by validating the string inside the reusable workflow, depending on type support in your feature set.