Connect GitLab

The common connection fields are described in Connect services.

1. Settings, GitLab, connection: set the server (https://gitlab.com or your own). Optionally set a base group, so paths below can be short (for example acme/platform).
2. Choose the token’s access: read only needs the read_api scope; read and write needs api, which commenting, approving, merging and rebasing use. The new-token link asks for the scope that matches.
3. In GitLab, create a personal access token with that scope. Export it, for example export GITLAB_TOKEN=glpat-...; env:GITLAB_TOKEN is the default. You can instead enter glab (radar uses the login of the glab program, and if GitLab turns that token down, radar asks glab to renew it once) or the token itself.
4. Add the groups or repositories you follow: FOLLOW in setup’s GitLab step, or Settings, GitLab, tenancies. Paste a group’s or repository’s link, or its path.

If GitLab refuses a write, radar shows GitLab’s reason. merged, closed in the connection sets how many days back views with state:merged or state:closed reach (14 by default).