Guides
How to coordinate workflows across repositories
A change in one repository needs to trigger builds in others.
5 min read
A change in one repository needs to trigger builds in others.
Why it happens
Workflows are repository-scoped, so cross-repository coordination needs explicit wiring.
How to fix it
- Use repository_dispatch to trigger downstream builds
- Authenticate with a GitHub App token rather than a personal access token
- Pass the upstream SHA so downstream builds are traceable
- Consider whether a monorepo would remove the coordination problem entirely
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.