GitLab / GitLab self-managed

An access-token connection to gitlab.com or a self-managed GitLab. Merge requests get a summary note, inline discussions and a commit status. GitLab has no per-line annotations and no blocking review, so those degrade. See the SCM provider docs.

This provider fills the scm slot. Configure it in Settings → Integrations, or during first-run setup.

Settings

Key	Field	Type	Required	Notes
host	GitLab host	text	No	Self-managed hostname, e.g. gitlab.yourco.com. Blank = gitlab.com.
accessToken	Access token	secret or reference	Yes	Group or project access token with api scope. Secret reference (env:NAME / file:/path). Reviews are posted as whichever user owns it.
orgId	Organisation	text	Yes	Every merge request reviewed through this connection bills and attributes to this organisation. GitLab groups are not linked individually.
webhookSecret	Webhook secret token	secret or reference	No	The token GitLab sends as X-Gitlab-Token on this instance’s inbound webhooks.

Note

2 fields are secrets (accessToken, webhookSecret). Pasted secrets are encrypted before storage. You can also supply a reference resolved when it is used. env:NAME reads a process environment variable; file:/run/secrets/name reads a mounted secret file.

What the connection test checks

Select Test connection to run a live test against the credentials you supplied. Saving validates and stores the configuration. Every check below is evaluated against the real service, not inferred from the configuration.

Check	Outcome
Authenticate with the access token (GET /user)	Must pass
Reach the v4 REST API on this host	Must pass

Adapter id: gitlab-scm.