Create your workspace
Register, verify your email, and create or join the organization that will own repositories, billing, alerts, and member access.
Customer documentation
BugSight Docs
Set up your workspace, connect repositories, understand review risk, and manage billing, security, and common repair workflows.
Start here
Getting started
Move from a new account to the first useful review signal without guessing which settings matter.
Connect GitHub or GitLab
Use the GitHub or GitLab connection flow from settings. Access should be completed by someone authorized to grant repository access for the organization.
Select repositories
Pick the repositories BugSight should monitor. Keep inactive or unrelated repositories disconnected so dashboards stay focused.
Run your first analysis
Open Commit Analyzer for a single commit or PR/MR Risk for a review URL. BugSight shows verdict, evidence, required actions, and reviewer guidance.
Integrations
Connect repositories
Connect GitHub or GitLab, select active repositories, and keep webhook and analysis health visible.
GitHub setup
Connect the GitHub App, sync repositories, and use GitHub checks/comments for native review visibility.
GitLab setup
Connect GitLab, select projects, and use provider-neutral MR analysis without GitHub-only assumptions.
Repository not visible
A missing repository usually points to provider permissions, installation scope, stale sync state, or an inactive connection.
Review decisions
Understanding risk results
Use the score, blast radius, checks, and reviewer guidance as review evidence. They are not replacements for engineering judgment.
- Changed-file evidence groups source, tests, docs, deployment, CI/CD, config, generated, and other areas.
- Blast Radius is review scope, not proof of impact. It should explain affected areas and checks in language that works for any repository stack.
- Required-check status separates observed check results from branch-protection or backup policy uncertainty.
- Reviewer recommendations use repository ownership and path familiarity when enough history exists.