Autofix PRs

Autofix PRs are optional. You can use auralogs as a logger with MCP access without connecting GitHub. Connect a repo later when you want auralogs to map incidents back to source code and open pull requests for review.

How it works

1. An error is detected and analyzed.
2. Your configured fix model (Claude Opus 4.6 or GPT-5 — set under Settings → Analysis → Model routing) reads the relevant source code from your repository.
3. It identifies the root cause and generates a code fix.
4. auralogs opens a pull request on your repo with the changes.

The PR includes:

• A clear title describing the fix
• A description with the error context and what was changed
• The minimal code diff to resolve the issue

Connecting your GitHub repo

Only connect GitHub when you are ready for source-aware analysis and PR generation.

1. Go to your project Settings on the dashboard.
2. Under Repository, click Connect Repository.
3. Authorize the auralog-autofix GitHub App for the specific repo you want to connect — auralogs only gets access to the repos you explicitly select.
4. Pick the repo from the list. The connection appears with the owner, name, and default branch.

Tip

auralogs uses a GitHub App with per-repository permissions. It only has access to the repos you explicitly select — not your entire GitHub account.

Dedup protection

auralogs tracks open autofix PRs to avoid creating duplicate fixes for the same error. If an error has already triggered a PR that’s still open, subsequent occurrences won’t generate another one.

Review before merge

Autofix PRs are opened for your review — they are never auto-merged. Treat them like any PR from a teammate: review the changes, run your CI, and merge when you’re satisfied.