What Traversal reads
- Merge requests — recent MRs, diffs, and discussions
- Commits — commit history and changed files
- Code — file contents and code search results
Setup
- Personal access token (recommended)
- Project access token
- Group access token
Create a token
- Go to User Settings > Access Tokens (gitlab.com/-/user_settings/personal_access_tokens)
- Click Add new token
- Set scopes:
read_api,read_repository, orapi - Click Create personal access token and copy the token immediately
Configure in Traversal
Go to Company Knowledge > Integrations, select GitLab, and paste the token.You can optionally scope access further:
- Use Project IDs for a comma-separated list of project IDs or project paths such as
mygroup/service-api - Use Group ID for group-wide access
https://gitlab.yourcompany.com. Do not include /api/v4. Traversal appends that path automatically.Self-hosted GitLab
For self-hosted instances, expand Self-Hosted Configuration and enter your GitLab host base URL (for example,https://gitlab.yourcompany.com). Do not include /api/v4. Ensure the instance is accessible from Traversal.
Required token scopes
- Read-only:
read_api+read_repository - Broader access:
api