Manage repositories and source access

GitHub installation access determines which repositories Uno can reach. Workspace attachment determines which of those repositories belong to a particular project. Complete both steps before expecting a repository in the session picker.

Attach a repositoryCopy Anchor Link

1. Open Settings → Integrations → GitHub and inspect the installation.
2. Grant the Uno GitHub app access to the repository through GitHub's installation settings.
3. Return to Uno and refresh the available repositories if needed.
4. Attach the repository to the workspace using the repository setup controls.
5. Inspect its setup and readiness information.

For an organization repository, a GitHub organization owner may need to approve or change the installation. Linking your personal GitHub identity does not itself grant the app access to every organization repository.

Select the working versionCopy Anchor Link

Before starting a session, review its branch or commit selection for each repository. A fixed commit is useful for reproducing an older result. A branch is useful for continuing work from a known development line.

For multi-repository work, select every repository the task needs and explain how they relate. A frontend and API can be attached to the same workspace without every session needing both.

Read readiness separately from accessCopy Anchor Link

A repository can be authorized and attached while its environment or snapshot is still building. Inspect snapshots and manifests for setup failures. Do not reconnect GitHub to fix a dependency-install error that already has a successful checkout.

If a repository disappears or fails authorization, verify the installation's selected repositories and the workspace attachment. Reconnect only when the app requests it or the connection is stale. Removing access can prevent new or continuing work from using that source.

See GitHub connection and permission troubleshooting.