meta-repo

Multi-repo orchestration lets you execute commands across all child repositories from a single control plane. You initialize a central .meta configuration, register your projects, and use plugin-based routing to apply commands consistently.

Migrating a monorepo into separate repositories is supported natively by splitting directories into independent repos while preserving history and continuity. The system uses a central .meta configuration to map and orchestrate these newly independent projects.

Yes, multi-repo workflows support fine-grained targeting. You can apply commands to a subset of repositories by using include and exclude filters within your central .meta configuration to control exactly which projects are affected.

To set up multi-repo orchestration, run meta init to create a minimal .meta configuration, then register your existing projects using meta project create or meta project import to establish the central control plane.

Multi-repo orchestration supports plugin-based command routing for common dependency tools. It includes specific plugins like meta npm and meta yarn, allowing you to keep dependencies synchronized across all registered child repositories.

Multi-repo orchestration adds a central .meta configuration layer, which is unnecessary for single-repository projects. If your team does not need to coordinate changes, run migrations, or synchronize dependencies across many repositories, this approach introduces avoidable overhead.