Multi-Repo vs. Monorepo: Cross-Language CI and Governance Integration

Integration Boundary

The Algorithms organization currently maintains 30+ independent language repositories (e.g., Python, Java, Rust, Go), each with its own CI pipeline, maintainer team, and contribution workflow. A proposed monorepo would consolidate all implementations under a single repository with unified governance.

Constraints and Uncertainty

Each language repo uses language-specific tooling (pytest, JUnit, Cargo test, etc.) with no org-wide CI standard. GitHub Actions minutes remain free for public repositories, so infrastructure cost is not a driver. However, cross-language consistency — shared linting rules, unified release tagging, and synchronized documentation — is currently managed through manual coordination across repos. The monorepo discussion has surfaced in org-level issues but lacks a migration plan, consensus on directory layout, or a strategy for preserving per-language CI isolation while enabling shared workflows.

Questions

1. What CI architecture would allow language-specific test suites to run independently while sharing common linting and governance checks in a monorepo?
2. How would maintainer permissions and code-review routing map from per-repo teams to a unified repository with path-based ownership?
3. What migration path preserves git history and issue tracking for each language without disrupting ongoing contributions?