multi-repo-setup

To set up a local environment for cross-repo workloads and match CI, clone or update each external repository into a build directory. This creates a reproducible workspace by pinning dependencies to origin/main or the current worktree to ensure CI parity before running tests.

The best way to manage multiple external repository dependencies is to resolve and pin them together in a single build directory. This approach mirrors CI pins and allows head-overrides, guaranteeing consistent, up-to-date local clones for cross-repo testing.

Yes, you can override a pinned dependency during cross-repo setup. The skill allows head-overrides to simpler/main or the current worktree, ensuring your local environment can test specific branch changes while maintaining overall workspace reproducibility.

Yes, the cross-repo setup includes steps to configure tooling and manage overrides of simpler. It actively verifies environment readiness after cloning or updating external repos, ensuring your build directory is fully prepared before you run any cross-repo tests.

You need to clone external repositories into a build directory when a workload spans multiple repos, such as depending on pypto, pypto-lib, and pto-isa. This ensures you have canonical local clones and CI parity before running cross-repo workloads.