Map a repository

Choose the repository

Check source-code status and select a repository granted to the workspace.

In Integrations, each row in Test or Live shows its source-code status. Use Connect source code to open an unmapped integration’s Source code tab, or Manage source code to review its repository and target branch. These links work before a mode receives data or has a connection. Members without owner or admin access can use View source code to inspect the mapping.

Repository access unavailable means the stored grant was revoked or the installation was suspended, disconnected, or uninstalled. Owners and admins can use Fix GitHub access to review workspace GitHub settings. Source code status unavailable means the list could not determine the mapping state; open Source code to inspect it. A connected status reflects stored access, not a live branch check or readiness to create a pull request. Repair preparation and delivery still verify the branch, observed commit, permissions, and approved patch.

Open the integration’s Source code tab and choose one repository from those granted to the workspace GitHub installation. Connecting GitHub grants access; saving this mapping links a repository to the integration. The repository, service path, and target branch are the same in Test and Live. You can configure them before receiving traffic. Credentials, observations, incidents, approvals, and repair runs stay in their own mode. Only active grants are selectable: a repository whose access was revoked, or whose installation is suspended or uninstalled, does not appear.

Choose the target branch

Choose where repair pull requests should be sent, independently of the observed deployment commit.

Choose Target branch for repair pull requests. A new repository selection starts with its default branch; an existing mapping keeps its saved branch. Search the loaded branches or use Load more branches to find later results. Saving verifies that the branch exists. A deleted branch stays visible as unavailable until you choose another branch.

The target branch is a delivery destination, not evidence of what is deployed. When observations report a commit SHA, repair preparation still checks that exact commit and compares source with the target branch. Changing the branch after preparing a patch requires preparing and reviewing it again.

• Repository mapping APIDiscover branches and manage mappings with a workspace API key.

Set the service path

Limit source context to the integration directory when needed.

Enter a service directory only when the integration is implemented below the repository root, such as services/payments. Path segments use letters, digits, dots, hyphens, and underscores; . and .. segments are rejected. Leave it empty when the repository contains one application at its root. For a monorepo, enter the integration’s folder, for example apps/api. This is a Git repository folder, not a URL or a directory on your computer. Saving verifies that it is a directory on the selected branch. Paths are relative to the repository root, without a leading slash.