# GitHub

> Connect your repositories so the Developer agent can ship branches and pull requests, and the Tech Lead agent can review them with a separate identity.

_CommerceCopilot documentation · Integrations_

GitHub is where CommerceCopilot's delivery agents do their work. Once connected, the Developer agent creates branches, writes code, and opens pull requests against your repository, and the Tech Lead agent reviews those pull requests before anything merges.

## Two bots, on purpose

The GitHub integration installs **two separate GitHub Apps**:

- The **Developer Bot** authors code: branches, commits, pull requests.
- The **Architect Bot** reviews: approvals, change requests, merges.

The split means a pull request is never authored and approved by the same identity. Your repository history shows a real review trail, the same branch protection rules apply to agents as to humans, and you can tell at a glance which agent did what.

## Connect GitHub

Setup happens on the **Settings** page and has three steps, shown on the GitHub card:

![The GitHub setup card showing the three-step flow: connect account, install Developer Bot, install Architect Bot](/docs/integration-github.png)

1. **Connect your GitHub account.** Click **Connect** and approve the OAuth request. This identifies your organization and lists your repositories.
2. **Install the Developer Bot.** You are taken to GitHub's app installation page. Install it on the account or GitHub organization that owns your repositories, and grant it access to the repositories the agents will work in. It needs read and write access to contents and pull requests.
3. **Install the Architect Bot.** Same flow, second app. It only needs pull request access; it never pushes code.

> **Prerequisite:** you need permission to install GitHub Apps on the account or organization that owns the repository. On company organizations this is typically an owner, or a member whose installation request an owner approves.

## Bind a repository to a project

1. Open the project and go to **Settings**, then **Integrations**.
2. In the **GitHub Repository** card, pick the repository this project's code lives in. Development stays paused until one is connected.

One thing to know: **once agents are actively working the project, the repository choice locks.** Agents hold branch state and in-flight pull requests, so switching repositories mid-delivery is deliberately prevented.

## What to expect in your repository

- Branches named per ticket, created from your default branch
- Pull requests authored by the Developer Bot, with the ticket's requirements in the description
- Reviews from the Architect Bot: approvals when the work passes, change requests with concrete comments when it does not
- Your branch protection rules, CI checks, and merge policies apply unchanged

## Troubleshooting

- **A red banner says an installation is missing or broken.** One of the two apps was uninstalled or lost access. Reinstall the affected bot from the GitHub card, on the GitHub account that owns your repository.
- **The repository picker does not show the repo you need.** The Developer Bot was not granted access to it during installation. In GitHub, open the app's installation settings and add the repository.
- **Pull requests appear under a personal account instead of the bot.** Finish steps 2 and 3 on the Settings card; without both apps installed, the integration falls back to your personal OAuth identity.

## Next steps

- [Jira](/docs/jira) or [Notion](/docs/notion) for the tickets the agents build from
- [Shopify](/docs/shopify) to give agents your storefront context

---
Canonical page: https://www.commercecopilot.ai/fr/docs/github