Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Connect GitHub to a Project
Computers, terminal and Git

Connect GitHub to a Project

Let Chetty work with GitHub as you, so a conversation can push a branch or open a pull request for the Project.

Before you start

  • The GitHub plugin is installed and available to your account.
  • You are a member of the Project.
  • Your GitHub account can read the repository that pull requests target and write to the repository that receives branches.

Connect your GitHub account

  1. Open Account → Linked accounts.
  2. Choose Connect GitHub. GitHub shows a One-time code.
  3. Open the GitHub verification page and enter the code.
  4. Return to Chetty and wait until the account shows Connected.

Repeat this only if the account shows Reconnect required.

Map a repository

  1. Open the Project and select its GitHub section.
  2. Choose Map repository.
  3. Fill in Base repository — the repository pull requests target — and Push repository — where branches go. They can differ for a fork.
  4. Choose Save mapping. The section then shows the mapping as Verified.

A Project has one mapping. Its creator or an administrator can remove it with Remove mapping.

What the mapping does

  • It applies to host and managed Projects.
  • Only your commands use your GitHub identity; another member's commands do not inherit it.
  • It stays in place for the Project until you or an administrator remove it.
  • A paired computer signs in to GitHub itself, so no mapping is stored for it.

Warning: Members of the Project share the mapping. Inside a managed environment they can see your GitHub token in running processes, so map a repository only where that is acceptable.

If it does not work

  • The account shows Not connected: choose Connect GitHub again and finish the code step.
  • The mapping is missing: you need to be a Project member, and the Project must be a host or managed Project.
  • A push is refused: check your access to the push repository and run Test connection in the account section.
  • Never paste an access token into chat.

Read Publish and review a branch for the next step, Autonomy & Safety to see when publishing is allowed.