GitHub

About

Connecting GitHub gives the Sazabi agent read access to the repositories you select, so it can cross-reference a stack trace with the actual source, see recent changes, and understand pull request context while investigating. GitHub is a forge integration; it can also open pull requests and, optionally, review new ones.

The agent can:

• Search and read source files in your connected repositories.
• Correlate errors with recent code changes and pull requests.
• Open pull requests with a proposed fix.
• Optionally review new pull requests with inline comments (see Set up automated code review).

Prerequisites

• A GitHub account that can install a GitHub App on the repositories you want to connect.
• Organization admin access in Sazabi.

Set up in the dashboard

You can change repository access later on GitHub under Applications > Installed GitHub Apps > Sazabi.

Set up with the CLI

You can also start the GitHub connection with the Sazabi CLI (installed and authenticated — see CLI reference).

GitHub connects through a browser flow — the CLI has no --credentials for it. Run:

sazabi integrations connect github

The command opens the Sazabi GitHub App install in your browser (sign in to the dashboard as the same user), then waits for the install to complete. In --json mode it prints an authorization URL to open instead of launching a browser:

sazabi integrations connect github --json

If the install needs approval from a GitHub organization admin, the connection appears once they approve — no need to rerun the command. After connecting, map repositories to a project — from the dashboard, or with the CLI: sazabi repos list shows the repositories available to the project and sazabi repos add <owner/name> links them for code search.

sazabi repos list
sazabi repos add acme/api acme/web

Run sazabi integrations list to confirm the connection.

Code search

Once GitHub is connected and repositories are mapped to a project, the Sazabi agent searches and reads those repositories to trace an error to the exact file and line during an investigation — cross-referencing a stack trace with the source that produced it. See Agent tools.

Automated code review

Sazabi can review pull requests on GitHub with inline comments and a verdict. Enable it with the per-project master switch under Settings > Code, then turn on this integration's own review toggle; request a review on demand by commenting @Sazabi review on a pull request.

See Set up automated code review for the full behavior — re-review on new commits, the on-demand request, and agent-opened pull requests.

Ask the agent from a pull request

GitHub is also an agent surface — a place you can start an agent thread and read its response without leaving GitHub. Mention @Sazabi in a pull request comment with any request (for example, "why did this test start failing?" or "summarize the risk in this change"), and the agent investigates using your connected repositories and project data, then replies in the same comment thread. Keep mentioning it in that thread to continue the conversation. This is separate from automated code review, which runs on its own — here you drive the questions.

Connected account

You can also connect your personal GitHub account under Settings > Connected accounts so the agent acts as you at GitHub. When you have a personal connection Sazabi uses it first and falls back to this organization integration otherwise. See Connected accounts.

Verify

Open Settings > Integrations > GitHub and confirm the connection reads connected and lists the repositories you selected. Then, in a thread in the mapped project, ask the agent to find a symbol or file you know exists in a connected repository — it should return the file. If code search returns nothing, confirm the repository is both installed on GitHub and mapped to the project.

Troubleshooting

Connection shows needs attention — The GitHub App installation may have been removed or its permissions changed on GitHub. Reconnect from Settings > Integrations > GitHub.

Agent can't find code it should see — Confirm the repository is mapped to the project you are working in; code search is scoped to a project's mapped repositories.

Pull request review isn't running — Review is a separate opt-in; see Set up automated code review.

Further reading