Skip to main content
Connecting GitHub gives the Superlog AI agent direct access to your source code. Once connected, the agent can inspect the files involved in an incident, push a fix branch, and open a pull request — all without you leaving your workflow. GitHub is optional: incidents are still detected and investigated without it, but the agent won’t be able to open PRs until a connection is active.

​
Why connect GitHub

When the agent identifies a root cause it needs two things to open a fix PR: read access to your repository so it can understand the affected code, and write access to push a branch and open the pull request. The GitHub App integration provides both in a single OAuth flow.

Code inspection

The agent reads your repository contents to understand the context around an incident before proposing a fix.

Automated fix PRs

When the agent finds a root cause, it pushes a branch and opens a pull request directly against your chosen base branch.

Auto-merge support

Configure Superlog to merge the PR automatically once all your CI checks pass, or immediately, or leave it for a human to review.

PR comments

The agent posts progress updates and investigation summaries as comments on the pull request and on related issues.

​
How to connect

1

Open Settings in the Superlog dashboard

Navigate to Settings in the left sidebar of your Superlog project.
2

Start the GitHub OAuth flow

Click Connect GitHub. You will be redirected to GitHub to install the Superlog GitHub App on your organisation or personal account.
3

Select repositories

Choose which repositories to grant the App access to. You can start with one repository and add more later from the GitHub App settings page.
4

Return to Superlog

GitHub redirects you back to the Superlog dashboard. The Settings page will confirm that GitHub is connected.
5

Grant repos to your project

Under Settings → GitHub Repos, select which of the installed repositories should be available to this specific project.

​
Permissions the App requests

Superlog requests the minimum permissions needed to read code and manage pull requests. No organisation-level or admin permissions are required.
Superlog never requests organisation administration, member management, or secrets access. If GitHub prompts for additional permissions beyond those listed above, do not approve — contact support.

​
PR settings

After connecting GitHub, you can tune how the agent handles the pull requests it creates. These settings live under Settings → Agent and are described in full on the Agent Settings page.
Set automerge_fix_prs to when_checks_pass to let Superlog merge fixes automatically once your CI suite is green, while still giving your existing branch protection rules the final word.

​
Refresh access

The Connect GitHub flow also authorises a commit-author identity so that Superlog’s commits appear under a recognisable name. If this token expires or you need to update the author identity, click Refresh access in Settings. This re-runs the commit-author OAuth flow without removing the App installation.
If you see ?gh=error after returning from GitHub during a refresh, try the flow again. If the error persists, contact support — the Superlog team can investigate the OAuth callback on the server side.

​
Disconnecting or changing repositories

To revoke access entirely, uninstall the Superlog GitHub App from your GitHub organisation settings (Settings → Applications → Installed GitHub Apps). To add or remove specific repositories without disconnecting, adjust them on the same GitHub App installation page and then click Refresh access in Superlog to sync the updated repo list.
Removing the GitHub connection does not delete any incidents, agent runs, or historical PR data in Superlog.

​
Next steps

  • Configure auto-merge and PR behaviour → Agent Settings
  • Set up Slack notifications so your team hears about fix PRs the moment they open → Connect Slack