Docs
Connections

GitLab

Connect gitlab.com with a read_api access token and read projects, commits, merge requests, issues, releases and pipelines.

A GitLab connection reads gitlab.com projects with an access token that has the read_api scope only. It calls only gitlab.com. Merge requests are read into the pull_requests table. For the tables, columns and limits that every forge shares, see the Git overview.

Preview

Git connections are in Preview and are enabled on request: contact support@xentropy.ai. Until GitLab is enabled for your account it is not offered in the forge selector, and its reads fail with PROVIDER_DISABLED.

Create a read-only token

A personal access token (it starts with glpat-) reads every project your account is a member of.

On gitlab.com, open Edit profile → Access tokens and choose Add new token.
Name the token and set an expiry date. GitLab requires one, at most a year ahead.
Select the read_api scope only.
Create the token and copy it.

To limit the connection to one group or project, create a group or project access token instead, with the read_api scope and the Reporter role.

Token permissions

The form lists this scope with a copy button.

ScopeUnlocks
read_apiRead-only API access to projects, commits, merge requests, issues, releases, tags, branches, contributors and pipelines

Set up the connection

Open Connections, choose New connection, then Git, and choose GitLab.
Name the connection and paste the token.
Choose Test connection. The stages are Authentication (the token) and Repository access. The test lists the projects the token can read.
Choose the projects to allow, or none to allow every project the token can read. Choose Save connection.
Open the connection, choose a resource, projects and a date range, pick fields, preview 100 rows and save a dataset.

Project full names are the path with namespace, such as acme/platform/api.

Connect with GitLab (sign-in with your gitlab.com account) appears only when GitLab sign-in is available for your account. Until then, connect with a token as above.

Resources

ResourceAvailableNotes
repositoriesYesProjects you are a member of
commitsYesThe default branch, or the branch you choose, in the date range, with line counts
pull_requestsYesMerge requests; number is the project-level ! number
issuesYesnumber is the project-level # number
releasesYesid is the release's tag
tagsYes
branchesYes
contributorsYesGitLab's contributor list, by name and e-mail
pipeline_runsYesPipelines created in the date range

Columns left empty

ResourceEmpty columns
repositorieslanguage, size_kb, pushed_at
commitsauthor_login
pull_requestsadditions, deletions, changed_files
releasesdraft, prerelease
contributorslogin
pipeline_runsactor_login, started_at, finished_at, duration_s

GitLab commits carry the author's name and e-mail but no login, and the contributor list has no login either. Name and e-mail are personal data, off by default. The pipeline list has no timings: use created_at.

Limits

gitlab.com allows 2,000 API requests per minute per user, and returns 429 with Retry-After when a limit is reached. Xentropy reads the RateLimit-* headers and waits for the reset. See Limits and refresh for pages, rows and deadlines.

Errors

ResponseCodeCauseWhat to do
401PROVIDER_ACCESS_DENIED, stage authThe token expired, was revoked, or was mistypedCreate a new token and choose Replace configuration
403PROVIDER_ACCESS_DENIED, stage permissionsThe token lacks the scope. details.missingScopes names it (read_api)Create a token with read_api; scopes cannot be added to an existing token
404NOT_FOUNDThe project does not exist, or the token cannot see it. GitLab answers 404 for projects you have no access toCheck membership, or the group or project the access token belongs to
RedirectNOT_FOUNDThe project moved or was renamedSelect the project under its new path
429RATE_LIMITEDThe rate limit is used upRetry after details.retryAt; scheduled refreshes wait by themselves

On this page