Reuse for GitHub Actionss
Reuse in GitHub Actions avoids copying the same YAML across repositories. A reusable workflow is a full workflow called by another with workflow_call, taking inputs and secrets. A composite action bundles several steps into one action that a job can use. Both keep pipelines consistent and easy to update.
Stage: Reuse and Extension · Part of the GitHub Actions roadmap · Last reviewed 19 November 2026
What to learn in Reuse
- Define a reusable workflow with inputs, secrets and outputs
- Call a reusable workflow from another repository
- Create a composite action from several run steps
- Choose between a reusable workflow and a composite action
- Pin reused workflows to a tag or commit SHA
Reuse interview questions
When would you use a reusable workflow instead of a composite action?
Use a reusable workflow to share whole jobs, including runner selection and multiple jobs. Use a composite action to share a sequence of steps inside a job. Reusable workflows cannot be nested very deep, while composite actions run in the caller's job.
How do you pass secrets to a reusable workflow?
Declare the secrets in the called workflow under workflow_call and pass them from the caller with a secrets block, or use secrets: inherit within the same organisation. This keeps the secret masked and available only where intended.
Where Reuse fits in the GitHub Actions roadmap
Reuse belongs to the Reuse and Extension stage (beginner level). Scale your automation.
Other units in this stage
Back to the full GitHub Actions roadmap