GitHub

Uno uses a GitHub app installation to access source repositories and deliver work. Your personal GitHub identity and the workspace's installation access serve different purposes.

Connect the installationCopy Anchor Link

1. Select the Uno workspace.
2. Open Settings → Integrations → GitHub.
3. Complete the connection flow and choose the GitHub account or organization that owns the code.
4. Grant the installation access to the required repositories.
5. Return to Uno and finish workspace repository setup.

For organization code, a GitHub organization owner may need to approve the installation or modify its repository selection. Confirm which account owns the installation before creating another one.

Attach repositories to the workspaceCopy Anchor Link

Granting GitHub access does not automatically attach every repository to every Uno workspace. Use the workspace's repository settings to select the project repositories. Refresh the available list after changing installation access.

Select the relevant attached repositories again when creating a session. Include multiple repositories when the goal spans them, then review each branch or commit selection.

See repositories and source access for readiness and environment setup.

Resolve changed accessCopy Anchor Link

If a repository is missing, inspect installation selection, your GitHub access, and workspace attachment. If a previously working repository fails authorization, check whether the installation was removed, suspended, or changed. Use the reconnect or refresh action shown in Uno.

A successful account link does not establish that source access is valid for a particular organization repository. Git commit attribution also does not replace installation authorization.

Review deliveryCopy Anchor Link

Ask the agent to create a PR when that is part of the task. Follow the published link, confirm the base branch and diff, and use your repository's review, checks, merge queue, and release process.

Use repository rules for conventions and GitHub routines for event-triggered work. See account security for personal GitHub identity and attribution.