Support Applications distributed across multiple repositories

Overview

Enable Radius Canvas to model and deploy one Radius Application whose workloads, infrastructure definitions, and deployment artifacts are distributed across multiple GitHub repositories.

Developers should be able to identify the repositories and branches that comprise an Application. Radius skills should analyze each repository, discover its components and dependencies, and combine them into a unified .radius/app.bicep application definition.

Radius Canvas should preserve the source repository, branch, commit, and file reference for every modeled resource. The Modeled, Planned, Deployed, and Diff views should represent the complete Application while making repository boundaries clear.

Deployment workflows should coordinate source revisions, builds, artifacts, permissions, and GitHub Actions workflows across all participating repositories. Radius should prevent deployment when required repositories or revisions are unavailable or inconsistent.

Expected outcomes

• Add multiple GitHub repositories to one Radius Application.
• Select a branch or commit for each repository.
• Generate one application definition from all selected sources.
• Preserve repository-specific source references in the Application graph.
• Detect dependencies and connections across repositories.
• Build and publish artifacts from the appropriate repositories.
• Coordinate deployment through GitHub Actions.
• Compare Application changes across repository revisions.
• Handle missing permissions, inaccessible repositories, and unpushed branches.
• Delete the complete deployed Application and associated resources.

Additional context

The current preview models and deploys one Application from a single repository. This roadmap item expands the source model while retaining one Radius application definition as the unified representation of the Application.

Start by examining Radius Canvas's current single-repository preview, application modeling, and deployment workflow. Define how repository and revision selection, cross-repository discovery, source references, permissions, artifacts, and GitHub Actions coordination should work across the Modeled, Planned, Deployed, and Diff views. Done means one application can be consistently modeled, deployed, compared, and deleted from multiple repositories while rejecting unavailable or inconsistent sources.