Cross-Repository Workflows

In modern software development, applications often consist of multiple components spread across different repositories. Think microservices, shared libraries, or separate deployment configurations.

Orchestrating workflows across these distinct repositories allows for greater modularity and separation of concerns. This lesson explores how to achieve this with GitHub Actions.

Traditionally, GitHub Actions workflows are scoped to a single repository. But what if you need:

• To build an artifact in one repo and trigger a deployment in another?
• A shared configuration repository to trigger updates in multiple service repos?
• To enforce security policies managed in a central repository across all others?

Cross-repository workflows provide the solution for these complex scenarios.