Question

Your organization maintains 15 microservice repositories on GitHub. Each repository currently duplicates the same 200-line CI job that builds a container, runs unit tests, scans for vulnerabilities, and pushes to a registry. You want to centralize this logic so that a change made once applies to all repositories, and you need the ability to pass secrets, run the shared logic as its own job with its own runner, and enforce required approvals on the shared deployment environment. Which approach should you implement?

Accepted Answer

Create a reusable workflow in a central repository and call it from each repository using the workflow_call trigger with 'uses' at the job level, passing secrets via 'secrets: inherit' or explicit secret inputs.

Answer

Convert the duplicated steps into a composite action stored in a central repository and reference it from a step in each repository's workflow.

Answer

Define the logic in a starter workflow template so each repository copies it into .github/workflows when the repo is created.

Answer

Store the shared logic in a custom Docker container action and invoke it as a single step within each repository's job.