One manifest for roughly 30 repositories
Team tooling
I built a manifest inspired by Android repo so an engineer can see the repositories they need and prepare the workspace with one command.
The problem
Our work spans roughly 30 independent repositories. To prepare for a task, engineers need to know which repositories belong together and how to set up the workspace consistently.
The manifest
I built a manifest inspired by Android repo that lists the repositories needed for a workspace and helps prepare them with one command. It gives the team one source for understanding the shape of the wider system without merging the code into a monorepo.
Why it matters
The repositories keep their own histories and release boundaries. The manifest makes it easier to see how they fit together and to create a workspace for cross-repository work.