GitHub

Install the GitHub App, pick a repo, and every ticket opens as a labelled issue with the screenshot inlined.

Every Rebase ticket can open as a GitHub issue in the repo you choose — labelled, with the screenshot inlined and the AI triage in the body — and status syncs both ways.

Connect

1. In the widget, open Settings → Integrations → GitHub.
2. Install the GitHub App — no personal access tokens to mint or rotate.
3. Pick the repository issues should file into.

What a ticket becomes

A structured GitHub issue, created the moment the ticket lands (or on demand from the ticket thread):

• Title and description, with the AI triage — summary, severity, repro steps, type — formatted in the body.
• The screenshot inlined in the issue itself.
• Labels: rebase, plus the classification as GitHub's conventional label — bug, enhancement or question.
• The suspected source location as a commit-pinned file and line reference when available — because Rebase can match captured context against your repo tree. See Source attribution.
• A link back to the full Rebase report.

Auto-create is a per-integration toggle; creation runs as a queued job with retries.

Status, both ways

• Close the issue in GitHub → the Rebase ticket resolves and its pin leaves the page.
• Reopen the issue → the ticket reopens.
• Resolve in Rebase → the GitHub issue closes.

Inbound sync arrives via signed webhooks, and each direction is toggleable.

Field mapping

Map Rebase priority and status onto your labels — your taxonomy, not ours. Configure it from the integration's settings in the widget.

The badge

Tickets linked to GitHub show their #number as a badge in the widget (owners and team only) — one click jumps to the issue.

Bonus: better source attribution

Connecting GitHub doesn't just receive issues — it makes tickets smarter. Captured paths, component names, test ids and button text are matched against your repo tree to produce commit-pinned permalinks in the suspected-source section.