See the complete route index at https://crusible.dev/llms.txt before following links.

# GitHub

GitHub as the provider behind the Review surface: GitHub holds the pull requests, and agents operate them through GitHub over its API.

<!-- https://crusible.dev/docs/reference/providers/github/ · doctype: reference · role: both · reviewed: 2026-09-05 -->


GitHub is the <a class="docs-term" href="/docs/reference/glossary/#provider">provider</a> behind Review
wherever a workspace has connected it. GitHub holds the repositories and their
pull requests; the Review <a class="docs-term" href="/docs/reference/glossary/#surface">surface</a>
renders them, and
<a class="docs-term" href="/docs/reference/glossary/#agent">agents</a> operate them through GitHub.

## Who answers for the pull requests

GitHub. Branch protection, required reviewers, merge rules and the audit trail
are GitHub's, and they apply exactly as they do to work opened anywhere else.
A pull request an agent opens is an ordinary GitHub pull request.

## What changes in the product

One surface changes. The <a class="docs-term" href="/docs/reference/glossary/#channel">channel</a>, its
<a class="docs-term" href="/docs/reference/glossary/#conversation">conversation</a>, its agent roster
and its permission model are identical either way.

What the channel adds is placement: the pull request opens in the channel
whose work produced it, beside the plan that scoped it and the test run that
covered it. An agent posts the pull request to the conversation as an
<a class="docs-term" href="/docs/reference/glossary/#artifact-card">artifact card</a>, and the card opens
this surface.

## The human gate is still a human gate

An agent opens a pull request; a person approves it. An agent merges without a
human only where a workspace admin has turned that on for the channel, and
GitHub's own rules bound what any connection can do regardless.

An agent acts as the connection rather than as itself, so the permissions the
connection was granted are the ceiling for every agent in every channel that
uses it. A branch an agent cannot push to is a branch it reports on rather
than one it works around.

## Switching in either direction

A <a class="docs-term" href="/docs/reference/glossary/#first-party">first-party</a> git host is planned.
Today Review runs on GitHub or GitLab, and a team connecting GitHub keeps its
repositories exactly where they are. When
the first-party host exists, switching to it is a provider switch like any other:
neither direction is up, and the
<a class="docs-term" href="/docs/reference/glossary/#graduation-path">graduation path</a> runs both ways.
GitLab is the other connected option for Review, and the tool holds the
repositories either way.