Issue
I need to know how Seer gets access to my repositories, including whether Sentry auto-adds repos, whether repos come from release tracking or other sources, and how code mappings and Connected Repositories affect access.
Applies To
All SaaS Customers using Seer
Seer
Resolution
Seer does not automatically discover repositories from release tracking or any other external source.
Seer can only use repositories you connect to a project. Connected repos are stored as Seer project repositories. Autofix uses those connected repos, not release tracking.
Code mappings (the same configuration used for stack trace linking) are related but separate. The API can surface repos from your code mappings, and the UI may show them when counting repos. They are not automatically turned into Seer’s connected repositories. If a project has no connected repositories, Autofix has no repos to use until you add them.
You can manually add any repository already connected through your GitHub or GitLab integration. Seer supports GitHub.com and GitLab.com (cloud only). Some features, such as coding-agent handoff, work with GitHub only.
To view or change which repositories Seer can access for a project:
Go to Project Settings > Seer, look for the project from Settings > Seer.
Look at the Connected Repositories section.
Use Add Repositories to Project to add repositories, or remove repositories you do not want Seer to use.
Settings > Seer is for managing projects and automation settings in bulk. It shows how many repos each project has. It does not bulk-edit the repository list. To change repos, open the project and use Connected Repositories.
Repos must be connected for Seer features that read or change code. If Code Review is not commenting on PRs, confirm the repo is in Connected Repositories. See Seer not commenting on PRs.
For code mapping setup, see stack trace linking and code mappings. For Seer setup, see Getting started with Autofix.