Code Repos
Connect Git repositories so analyses include code correlation
The Code Repos page manages connections to GitHub, GitLab, and Bitbucket. For platform-specific setup walkthroughs, see Code Repositories.
What's on the page
A list of all repo connections for this project, each showing:
| Column | Notes |
|---|---|
| Platform | GitHub / GitLab / Bitbucket icon |
| Repos count | How many repos this connection covers |
| Auth type | App / OAuth / PAT (or App Password for Bitbucket) |
| Lookback | PR history window in days |
| Status | Active / Inactive |
| Actions | Edit, Flush cache, Toggle active, Delete |
Adding a connection
Click Connect repository to open the platform picker. Pick GitHub, GitLab, or Bitbucket. For each:
- The recommended path is App / OAuth — opens the platform's authorization flow in a new window
- A fallback Personal Access Token form is also available
After authorization, you're redirected back with oauth_success in
the URL and the connection appears in the list. Configure repos to
include and (optionally) service mappings, then save.
Service mappings
Inside the Edit view, the Service mappings section is a table with one row per mapping:
| Column | Purpose |
|---|---|
| Service name | The exact value from your logs' service field |
| Repository | Which connected repo this service lives in |
| Path prefix | Subdirectory inside the repo (for monorepos) |
| Default branch | What branch to read from |
Add as many rows as you have services. See Service mappings for details.
Flush cache
Repo file contents are cached for performance. The Flush cache action clears the cache for that repo connection — useful if you've made structural changes and want to ensure the next analysis reads fresh content.
Required role
| Action | Required permission |
|---|---|
| View list | config:read |
| Add / edit / delete | config:write |
| Flush cache | config:write |
Quotas
| Plan | Repos per project |
|---|---|
| Starter | 1 |
| Pro | 5 |
| Business | 10 |
| Enterprise | Unlimited |