GitLab
Published on May 25th, 2026Introduction
The Context Store has several GitLab templated Data Sources to allow users to quickly pull relevant data into their Data Store. These templates are a starting point and often you'll want to apply filters or chained Data Sources to modify these templates to suit your needs.
Authentication
The built-in gitlab integration is token-based, using a Personal Access Token (PAT).
Pre-built Data Sources
This table lists the GitLab API permissions needed for the GitLab data source seeds currently defined in this repo.
Permissions below are expressed as GitLab Personal Access Token scopes.
| Data source seed | GitLab endpoint(s) used | Recommended PAT scope(s) |
|---|---|---|
GitLab projects | GET /api/v4/projects | read_api |
GitLab groups | GET /api/v4/groups?all_available=true | read_api |
GitLab merge requests | GET /api/v4/projects then GET /api/v4/projects/{id}/merge_requests?state=opened | read_api |
GitLab issues | GET /api/v4/projects then GET /api/v4/projects/{id}/issues?state=opened | read_api |
GitLab group members | GET /api/v4/groups then GET /api/v4/groups/{id}/members | read_api |
GitLab project members | GET /api/v4/projects then GET /api/v4/projects/{id}/members/all | read_api |
GitLab tags | GET /api/v4/projects then GET /api/v4/projects/{id}/repository/tags | read_api |
GitLab releases | GET /api/v4/projects then GET /api/v4/projects/{id}/releases | read_api |
GitLab pipelines | GET /api/v4/projects then GET /api/v4/projects/{id}/pipelines | read_api |
GitLab environments | GET /api/v4/projects then GET /api/v4/projects/{id}/environments | read_api |
GitLab deployments | GET /api/v4/projects then GET /api/v4/projects/{id}/deployments | read_api |
For all current GitLab seeds, read_api is typically sufficient.
If you ingest additional repository content endpoints later, you may also need:
read_repository
