Setting up Gitlab as a Source
Connecting GitLab as a Source in Guru allows you to bring your GitLab issues into Guru for searching and generating AI-powered Answers. This integration helps your team access code and related content directly within Guru, improving knowledge sharing and reducing context switching.
Access RequiredGuru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources.
Gitlab Issues You need your Gitlab Issues credentials
Setting up GitLab Issues as a Source
- Go to Manage > Sources in the Guru web app.
- Select GitLab Issues from the list of available Source icons.
- Click Configure Integration.
- Optionally, rename the Source to something meaningful for your team.
- Click Next.
- Click Connect and log in to your GitLab account to authorize Guru.
- Add a display name for the Source (optional) and click Connect Source.
- Assign which Guru Groups should have access to this content.
Objects synced from Gitlab Issues
Primary objects are the objects used to generate the search record.
| Common Model / What You'll See During Setup | Objects/Data Brought In | Key Fields |
|---|---|---|
| Ticket | Primary Object: Project issues and tasks | ⢠Name (title) ⢠Description ⢠Ticket type ⢠Status (Enum: opened/closed) ⢠Priority (Enum) ⢠Assignees (Array) ⢠Due date ⢠Completed at ⢠Project (Unknown) ⢠Collections (Array - groups/projects) ⢠Tags (Array - labels) ⢠Ticket URL ⢠Remote created at ⢠Remote updated at ⢠Remote ID ⢠Remote data |
| Comment | Notes/comments on issues | ⢠Body ⢠User (UUID - author) ⢠Ticket (UUID) ⢠Remote created at ⢠Remote ID ⢠Remote data |
| Project | GitLab repositories/projects | ⢠Name ⢠Description ⢠Remote ID ⢠Remote data |
| Collection | Groups and subgroups organizing projects | ⢠Name ⢠Description ⢠Access level (Enum) ⢠Parent collection (UUID - parent group) ⢠Users (Unknown) ⢠Remote ID ⢠Remote data |
| Tag | Labels for categorizing issues | ⢠Name ⢠Remote ID ⢠Remote data |
| User | GitLab users (developers, maintainers) | ⢠Name ⢠Email address ⢠Avatar ⢠Is active (Boolean) ⢠Remote ID ⢠Remote data |
| Role | User roles and permissions within groups/projects | ⢠Name ⢠Remote ID ⢠Remote data |
Setting up GitLab Repository as a Source
- Go to Manage > Sources in the Guru web app.
- Select GitLab Repository from the list of available Source icons.
- Click Configure Integration.
- Optionally, rename the Source to something meaningful for your team.
- Click Next.
- Click Connect and log in to your GitLab account to authorize Guru.
- Choose which repositories or bulk select all repositories within the selected Groups and Projects.
- The Source will index text-based source files fully and only index the titles of binary files (e.g., .zip files).
- Click Finish.
- Select the Guru Groups that should have access to this GitLab Source.
- Optionally, assign a Source Owner who can manage this Source later.
- Click Connect Source to finalize the setup.
What gets synced
- Source code files from the selected GitLab repositories
- Only text-based files are fully indexed; binary files are indexed by title only
Permissions
- When you connect Gitlab as a source in Guru, you'll permission that content in Guru. Learn more here.
- If someone is not provided with access in Guru to this source, they will not see Gitlab results in searches or when chatting with Guru.
Updated 4 months ago
Did this page help you?
