Skip to main content
The GitLab connection is token-based and read-only: you give Momentic an access token, and it reads project, branch, commit, and merge-request metadata through the GitLab API. Momentic does not write to GitLab: no comments, no merge requests, no pushes.

​
What the connection reads

​
Install

  1. Open Settings > Integrations in the dashboard.
  2. Click Connect on the GitLab card.
  3. Paste an access token and your GitLab instance URL (for example https://gitlab.com or your self-managed base URL).
The token’s own scope decides which projects Momentic can see; there is no project picker. A token that reaches three projects connects all three.
GitLab integration settings

GitLab integration settings

​
Which token to use

Required scope: read_api (the broader api scope also works).

​
Gotchas

  • Token expiry. Project and personal tokens carry a GitLab expiry date. When the token lapses, Momentic can no longer resolve branches or MRs; rotate the token in GitLab and paste the new one into the integration card.
  • PAT visibility. A personal token exposes every project its owner can read. Prefer a project access token when one project is enough.
  • Self-managed instances. The instance URL must be reachable from Momentic’s services; a cloud connection cannot reach a VPN-only GitLab.
  • Runs still start in CI. GitLab does not trigger Momentic runs. Run the CLI from your pipeline: see GitLab CI/CD for the ready-to-paste job.

​
Disconnect or revoke

  • Disconnect on the GitLab card in Settings > Integrations.
  • Revoke the token under the user’s or project’s Settings > Access tokens in GitLab. Revoking takes effect immediately; the Momentic side shows the connection as broken until you replace it.