Skip to documentation
Code Voucherby Pyratz
Open
Browse documentation
TutorialQuickstart

Complete your first Code Voucher review

Connect one GitLab project, let Code Voucher publish a pipeline-scoped review status, and inspect a durable review verdict.

First-party dogfood alpha. The GitLab path is running on Code Voucher's own repositories but is not yet accepted for customer private beta. GitHub support is planned behind the same provider abstraction.

Before you begin

  • A Code Voucher workspace that will own the repositories, private runs, teammates, and integrations
  • A GitLab project with merge request pipelines enabled
  • A dedicated GitLab service account with Maintainer or Owner access to the project
  • Owner or administrator access to the Code Voucher workspace
  • For agentic QA: a deterministic local application environment

Installation

  1. 1

    Create the workspace

    Continue with GitLab, then name the Code Voucher workspace that will own the review configuration. GitLab sign-in identifies you; it does not grant Code Voucher access to your repositories.
  2. 2

    Connect the service account

    Follow Connect GitLab to add a dedicated GitLab account to the workspace. Its token—not your login—controls repository access and the identity used for review comments.
  3. 3

    Discover and enable the repository

    Open Repositories, refresh the projects visible to the service account, and choose Enable. Code Voucher creates and manages the webhook secret, installs the managed GitLab hook, and verifies the connection before accepting events.
  4. 4

    Require successful GitLab pipelines

    In GitLab, enable Pipelines must succeed for the project. Code Voucher publishes a pending, passing, or failing review status directly to the merge request pipeline.
  5. 5

    Open a merge request

    Push a focused source change and open a merge request. The managed webhook creates the review; no Code Voucher YAML, setup merge request, or dedicated runner is needed.
  6. 6

    Wait for the review status

    The pipeline displays code-voucher/review. It remains pending while the review runs, then passes or fails the same merge request pipeline.

Optional: native CI bridge

Use the advanced bridge only when you need Code Voucher represented as a native CI job. Choose Set up CI from repository details to prepare a setup merge request. Direct status publishing stays active until that MR is merged and a re-check verifies the managed configuration on the default branch.

Run and inspect the first review

  1. 1

    Open a small merge request

    Push a focused source change to the connected GitLab project and open a merge request pipeline.
  2. 2

    Wait for code-voucher/review

    The external status reflects durable Code Voucher state on the exact merge request pipeline.
  3. 3

    Open the private run

    Follow the dashboard link and inspect the verdict, accepted findings, rejected observations, scope, and verification evidence.
Code Voucher run page showing a completed review and its findings
The completed run separates the trusted verdict and accepted findings from rejected model observations.

You are done when

  • The GitLab merge request pipeline contains a code-voucher/review status
  • The review status reaches a terminal result
  • The dashboard run matches the merge request commit SHA
  • Private findings are visible only to active members of the owning Code Voucher workspace

Continue learning

Understand how a run moves through the system, then analyze the repository with the setup assistant. Continue with the Agentic QA repository contract.