Back to all integrations

Source control

Lineman and GitLab

The same repository attribution and per-issue write-back, for self-managed and hosted GitLab.

Read the setup guideView all integrations

What this gets you

Connect GitLab once and Lineman knows which project and branch each piece of AI work belongs to. On the projects where you allow it, Lineman writes each issue's running AI cost back onto that issue as a note. The same attribution and write-back run against a self-managed instance on your own domain as well as gitlab.com. Spend on a project you have not authorised is flagged, so AI usage outside the work you expected stands out instead of blending in.

What people use it for

  • Cost totals on the issue

    Name a branch feature/#412-retry-backoff and issue 412 carries the cumulative AI cost of that work as a note, covering everyone who has worked on it. Lineman matches a hash followed by a number, so a bare number in a branch name is not picked up. If your team already brands branches with bare numbers, set a custom matching pattern on the integration. Issue numbers are per project, so a #412 in another project keeps its own separate total. Each update edits the same note in place instead of adding another, and an unchanged total is skipped, so nobody is notified about a number that did not move.

  • Self-managed and gitlab.com alike

    Enter your own instance host, for example gitlab.acme.internal, and attribution works the same way as on GitLab SaaS. There is no default host, so a self-managed customer's token is never sent to a server that is not theirs. The host must be https. A plain http host is rejected when you connect. Lineman then discovers the projects your GitLab identity can see, along with their default branches, so there is nothing to configure inside GitLab itself.

  • Flag spend on unauthorised projects

    Tick the projects where AI spend is expected. Spend Lineman sees on a project you have not ticked is flagged for you to look at. Letting Lineman write notes on a project's issues is a separate tick, so you can attribute a project's cost in Cost Explorer without it writing anything into GitLab.

More in Source control

Set up GitLab

The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.

Read the setup guide

Looking for something else?

Every integration in one place, searchable by name and filterable by what it does.

View all integrations