Integrating Sazabi with GitHub
Connect GitHub repositories so Chat can read your code and provide better debugging context.
Learn how to connect Sazabi to GitHub so Chat can access your source code when investigating production issues.
About the Sazabi integration for GitHub
The Sazabi integration for GitHub gives Chat read access to your repositories. When you are debugging an issue, the assistant can look at the relevant code to understand what might be causing the problem.
With the Sazabi integration for GitHub, the assistant can:
- Read source files to understand how your code works.
- Look at recent changes to correlate bugs with code modifications.
- Examine pull request context to understand what changed and why.
- Cross-reference stack traces with actual source code.
Prerequisites
Before you connect GitHub, make sure you have:
- A Sazabi account. Request access at sazabi.com
- A GitHub account with access to the repositories you want to connect.
Installation
Start the connection
Click Connect GitHub. Sazabi redirects you to GitHub to authorize the Sazabi GitHub App.
Authorize the app
Review the permissions requested by the Sazabi GitHub App and click Authorize to grant access.
Select repositories
Choose which repositories to grant Sazabi access to. You can select all repositories or choose specific ones.
You can always change repository access later in your GitHub settings under Applications > Installed GitHub Apps > Sazabi.
Permissions requested
The Sazabi GitHub App requests the following permissions:
| Permission | Access | Purpose |
|---|---|---|
| Repository contents | Read | Read source files to provide code context during debugging. |
| Pull requests | Read | Access PR descriptions and changes to correlate issues with recent modifications. |
| Issues | Read | Reference issue context when investigating related production problems. |
Sazabi only requests read access. The integration cannot modify your code, create commits, or make changes to your repositories.
Using GitHub context in conversations
Once GitHub is connected, the assistant can reference your code when you ask questions. You do not need special syntax; just describe what you want to know.
Examples
Ask the assistant to look at specific code:
Look at the checkout service code and find what could cause a null pointer exception.Correlate production issues with recent changes:
What changed in the last PR to payment-api that could explain these timeout errors?Cross-reference stack traces:
Here is the stack trace from the error. Can you look at the source code and explain what is happening?Understand how code works:
How does the user authentication flow work in our codebase?The assistant will read the relevant files and provide answers with specific references to your source code.
Troubleshooting
Cannot see a repository
If the assistant cannot access a repository:
- Go to your GitHub settings at Settings > Applications > Installed GitHub Apps.
- Find Sazabi and click Configure.
- Verify the repository is in the list of accessible repositories.
- If using organization repositories, ensure the Sazabi app is approved for the organization.
Permission denied errors
If you see permission errors when the assistant tries to read code:
- Disconnect the GitHub integration in Sazabi settings.
- Reconnect and re-authorize with the correct scopes.
- Make sure you have read access to the repository in GitHub.
Repository access not updating
GitHub App permissions can take a few minutes to propagate. If you just changed access settings:
- Wait a few minutes and try again.
- If the issue persists, disconnect and reconnect the integration.
Security considerations
- Sazabi only has read access to your repositories. It cannot modify code or settings.
- Code is accessed on-demand during conversations. Sazabi does not clone or store copies of your repositories.
- Access is scoped to the specific repositories you select during installation.
- You can revoke access at any time from your GitHub settings or the Sazabi dashboard.