Connect and map repositories
Give Vörr the code context and ownership mappings it needs to answer repository-level and cross-system questions.
Before you start
Confirm that:
- The required workspaces and environments already exist.
- You can authorize the relevant GitHub or GitLab organization.
- You have access to the repositories you want Vörr to index.
Connect the Git provider
Open the repository step in onboarding, or Git Integration after onboarding. Choose your provider and select Connect GitHub, Connect GitLab or Connect Bitbucket.
The connection window opens in a new tab and this page updates once you finish. Vörr reads repository metadata only — it never pushes code or changes your repositories.

Select repositories
Toggle the repositories Vörr should track — the rest are ignored. Use the search field, or Select all, for large organizations.
Connect all repositories that participate in the same product or service flow. A repository that is not connected is outside Vörr's knowledge, and Vörr will identify that limitation rather than infer its contents.

Map each repository to a workspace
Assign each repository to the team or workspace that owns it. This gives Vörr organizational context as well as code context.
Map branches to environments
Associate important branches with their deployment environments so Vörr can interpret which version of the code belongs to each environment.
- main → Production
- develop → Staging
Wait for indexing
Vörr indexes committed repository code. Local, uncommitted work on a developer's machine is not included.
Confirm the connection
Check that:
- The expected repositories appear in Vörr.
- Each repository has a workspace.
- Important branches have environment mappings.
- Indexing has completed successfully.
