GitHub

Use GitHub setup when your TeaHouse needs repository-aware team workflows.

The GitHub integration is separate from your local Git setup. Your terminal still uses the Git remote, SSH keys, credential helper, and gh or Git commands already configured on your machine.

What GitHub setup is for

Depending on what your workspace enables, GitHub can support workflows such as:

• Confirming repository access for team or background-agent flows.
• Connecting repository identity to a Coldtea project.
• Supporting PR, deployment, or Matcha-related flows where configured.
• Returning users to Coldtea after an install or auth handoff.

Do not assume every GitHub-backed workflow is available in every build. If a page or action is missing, the feature may not be enabled for your TeaHouse.

Before you connect

Check three things:

• You are signed in to the right Coldtea TeaHouse.
• You are signed in to the right GitHub account in the browser.
• That GitHub account can install or manage access for the target repository.

If you cannot grant repository access in GitHub, Coldtea cannot work around that from the desktop app.

Connect GitHub

The usual flow is:

1. Open the GitHub integration surface in Coldtea.
2. Start the connection or installation flow.
3. Complete the GitHub browser handoff.
4. Grant access to the repositories your team wants Coldtea to use.
5. Return to Coldtea and wait for the status to show connected.

For repository-scoped features, installing the app is not enough. The GitHub app also needs access to the specific repository.

If access looks wrong

Check in this order:

• The active TeaHouse is the one where GitHub was connected.
• The browser completed the connection successfully.
• The GitHub App is installed for the organization or account you expected.
• The target repository is included in the installation's repository access.
• Your GitHub account has permission to manage that installation.

If the local terminal cannot push or fetch, debug local Git credentials instead. GitHub integration status does not replace your normal Git remote setup.

Security note

Grant the smallest repository access that supports the workflow. Team integrations may sync selected repository, task, PR, deployment, or QA metadata depending on the feature used.

Next: Linear or teams and security.