Guides
How to use reusable workflows at scale
Fifty repositories have fifty slightly different copies of the same pipeline.
5 min read
Fifty repositories have fifty slightly different copies of the same pipeline.
Why it happens
Copy-paste is the default sharing mechanism, so improvements never propagate.
How to fix it
- Publish a reusable workflow and call it with workflow_call
- Version it with tags so repositories can upgrade deliberately
- Expose inputs for the parts that genuinely differ, and nothing else
- Use composite actions for step bundles and reusable workflows for whole pipelines
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.