Skip to main content
The GitLab integration syncs issues and merge requests from your selected projects into Jinzo’s entity store. GitLab data becomes searchable locally and available as context in AI chat. Both gitlab.com and self-hosted instances are supported.

​
Authentication

GitLab uses a Personal Access Token (PAT) with the read_api scope for authentication. The token is stored encrypted in the local database.
Jinzo requires only read_api access. No write operations are performed against your GitLab instance.

​
What Gets Synced

FieldDetails
Entity kindissue, merge_request
Resource kindgitlab_project
Data syncedTitle, description, state (open/closed/merged), labels, assignee, issue/MR number, draft status
Both issues and merge requests are synced as separate entity types. Merge requests include draft status detection. Relative image URLs in descriptions are resolved to absolute URLs automatically.

​
Setup

1

Generate a Personal Access Token

In GitLab, go to Settings > Access Tokens and create a new token with the read_api scope.
2

Connect GitLab

Go to Settings > Apps in Jinzo and click Connect next to GitLab. Enter your GitLab domain (defaults to gitlab.com for cloud, or enter your self-hosted domain) and paste your access token.
3

Select Projects

Choose which GitLab projects to sync. The project list shows the full namespace path and visibility (private or public).
4

Initial Sync

Jinzo fetches existing issues and merge requests from selected projects. Subsequent syncs happen incrementally.

​
Self-Hosted Instances

Jinzo supports self-hosted GitLab installations. During setup, replace gitlab.com with your instance domain (e.g., gitlab.mycompany.com). The token and API calls will target your custom domain.