Interrepository

Interrepository is a term used in software development to describe the coordination, interaction, or operation across two or more separate repositories. It encompasses activities such as cross-repository dependencies, federated workflows, and data or artifact sharing between repositories that may be managed independently.

The scope of interrepository includes version control repositories (for example, Git or Mercurial), as well as artifact repositories and data stores used by a project. Common mechanisms include declaring dependencies on packages or modules stored in other repositories, linking or integrating external repositories through submodules or subtree strategies, and coordinating continuous integration and delivery pipelines that span multiple repositories. Interrepository practices can also involve federated searching, mirroring, and synchronized updates to ensure compatibility across components.

Use cases for interrepository arise in polyrepo environments where teams manage distinct repositories for different services or libraries. Examples include microservices architectures with separate codebases, shared libraries consumed by multiple projects, or open-source ecosystems where projects rely on dependencies hosted in external repositories. Interrepository workflows enable independent development and governance while maintaining cohesive builds and releases.

Common approaches and patterns include using submodules or git subtree procedures to incorporate external repositories, relying on external package managers and artifact repositories for cross-repo dependencies, and implementing CI/CD pipelines that automate cross-repository tests and deployments. Tools and practices aim to minimize drift, enforce stable interfaces, and provide clear provenance of changes across repositories.

Challenges in interrepository work include dependency version drift, compatibility guarantees, security and access control, and the complexity of coordinating releases. Sound practices emphasize explicit version pinning, automated testing across repositories, thorough documentation, and robust tooling to manage cross-repo changes.

See also: monorepo, polyrepo, submodule, git subtree, dependency management, artifact repository, CI/CD.