Start by marking exactly what is duplicated. A composite action bundles steps inside a job. A reusable workflow lets callers share a workflow that can contain several jobs.


Keep shared setup close to the caller


Suppose two jobs both install a tool and configure a local cache, but run different tests afterward. A composite action can package those setup steps, and each caller can still add its tests in the same job. If the team needs to share build and test as distinct jobs, put that process in a reusable workflow and call it at the job level.


Migrate one caller first


Write down the old workflow’s expected inputs, outputs and failure messages. Move one caller and compare the new run with a baseline. Confirm that a successful run still exposes the expected outputs and that a deliberately failing test still fails the appropriate job. Leave the other callers on their existing setup until that comparison passes.


Write down what a caller needs to control. If it must add a step after setup and share the same working directory with that step, keep that work in the caller’s job and call the composite action from a step. If the shared process must select its own runners, run multiple jobs or report individual jobs to reviewers, a reusable workflow gives that process room to define those boundaries.


For a migration test, use one repository with a known-good run and a deliberately failing run. Compare the job names reviewers see, whether the same test logs are reachable, and whether a downstream job still receives the output it uses. With a cross-repository reusable workflow, confirm what was checked out: GitHub documents that checkout inside the called workflow defaults to the caller’s repository. Use a stable revision during rollout so future edits to the shared definition do not change all callers unexpectedly.


https://docs.github.com/en/actions/concepts/workflows-and-actions/reusing-workflow-configurations