What this section is for
Connect a Git provider with a token and choose repositories to analyse. After saving, start the first sync from the connection card. Saving alone does not start it; background updates depend on the configured schedule.
When to use
- When connecting your first repository.
- When analytics is empty or has stopped updating.
- When replacing a token or changing the repository list.
Quick start
- 1Create a token with the documented scopes: repo and read:user for GitHub, read_api and read_user for GitLab.
- 2For Bitbucket, use an API token with basic auth โ your Atlassian email in the email field and the token below it. OAuth bearer tokens are a different mode and are not interchangeable.
- 3For a self-hosted instance, fill in the server URL; leaving it empty uses the public endpoint.
- 4Save the connection, enable the repositories that matter, run the first sync, and check the last sync time.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Personal access token | Authenticates against the provider on your behalf. | Follow the permission guidance for your provider. If you use a service account, make sure someone is responsible for its token. | Expecting a read-only token to post comments or perform other automation actions. Those need additional permissions. |
| Server URL | Points the connection at a self-hosted instance instead of the public one. | Enter the full server address, including https://. Check that it points to your Git provider installation. | Entering a repository page or API URL instead of the server address. |
| Enabled repositories | Selects which repositories are analysed. | Start with one active team repository. Add the others after checking its data. | Including archived or third-party code and treating its history as current team work. |
Usage example
Scenario: No new data has appeared in the team overview for several days.
- 1Open this page and read the last sync time for each connection.
- 2Run a sync manually and check its completion status.
- 3If it fails, check token expiry, permissions and server availability. Fix the problem and sync again.
What this shows: You have checked the connection and can distinguish a sync failure from a period without new changes.
FAQ
Do you read our source code?
Analytics reads commit, pull request and review metadata. Technology detection also uses the file tree and selected dependency and configuration files, such as package.json, go.mod and Dockerfile. A complete copy of the source code is not downloaded. Tokens are encrypted in storage.
How often does it sync?
Git integrations refresh automatically on a schedule of roughly half an hour by default, and you can trigger a sync manually at any time.
What happens if I delete a connection?
Syncing stops. Commitlane deletes the connection, its synced repositories and their commit and pull request records. The original repositories at your Git provider are unchanged. To continue with a new token, update the connection instead of deleting it.
Tips
- Record token expiry dates and replace tokens before they expire. If data is stale, check sync status first.
- Check one repository against your Git provider before adding the rest.