Skip to documentation
Code Voucherby Pyratz
Open
Browse documentation
How-to guideIntegrations

Connect a GitLab service account

Give one Code Voucher workspace durable repository access and an identity for review statuses and comments.

What this connection controls

GitLab sign-in uses a transient read_user OAuth token only to identify a teammate. It does not grant repository access. The service-account token configured here belongs to the workspace and controls repository discovery, code reads, managed webhooks, CI setup, review statuses and comments. A teammate can use Code Voucher without having personal access to every connected repository.

Default merge gate

After you enable a repository, Code Voucher uses this account to post a pipeline-scoped code-voucher/review status to each merge request. Enable GitLab's Pipelines must succeedmerge check to require a passing review. This default needs no CI YAML, setup merge request, or dedicated runner.

If a repository previously used the native CI bridge, choose External status in repository setup. Code Voucher opens a managed removal merge request and switches the active mode only after the default branch is verified without the managed bridge.

Before you begin

  • A dedicated GitLab bot or service-account user
  • Owner or administrator access to the Code Voucher workspace
  • Maintainer or Owner access for the service account on every project to connect
  • A personal access token with the api scope and a deliberate expiry date

Connect the account

  1. 1

    Prepare the GitLab user

    Add the dedicated user to the required GitLab groups or projects at the eligible access level. Discovery excludes lower-access projects.
  2. 2

    Create the token

    In that user's GitLab preferences, create a personal access token with the api scope and a deliberate expiration date. Copy it once.
  3. 3

    Open workspace settings

    Choose the correct workspace, then open Settings. Under GitLab service account, paste the token and choose Validate and connect.
  4. 4

    Verify the identity

    Confirm that Settings shows the expected GitLab username, token prefix, api scope, and expiry. The full token is encrypted at rest and is never displayed again. Review comments will be posted by this account.
  5. 5

    Add repositories

    Open Repositories, refresh discovery, and enable only the projects this workspace should own.

Rotate or remove access

Create a replacement token on the same service account, choose Validate and replace in Settings, and verify the new prefix, scope, and expiry before revoking the old token. Removing the connection deletes Code Voucher's stored capability but does not revoke the token in GitLab; revoke it there as well. Existing private runs remain owned by the workspace.