TIA shared baseline support for GitLab?

[nicci296]

The shared baseline is very intriguing, but we use a self-hosted GitLab Repo.

Are there any plans to introduce GitLab CLI support as well in the near future?

[dhrupo]

Yes — this shipped. GitLab baseline support was added in #1841 and released in v5.2.0 (merged and tagged 2026-09-14), so a self-managed instance works today.

Two things are worth knowing for self-hosted, both from src/Plugins/Tia/Baselines/GitLabRemote.php on 5.x:

1. Self-hosted needs the glab CLI; gitlab.com does not. detect() returns the project path straight away when the remote host is gitlab.com, but for any other hostname it first requires glab on the PATH:

if (strcasecmp($hostname, 'gitlab.com') === 0) {
    return $path;
}

if (! $this->cliExists()) {
    return null;
}

So install glab and run glab auth login, pointing it at your own host. The token needs the read_api scope — Pest says so itself when a call is refused: "access denied — check that your glab token has read_api scope."

2. The CI job must be named tia-baseline and run on the default branch. The lookup matches both:

if (($job['name'] ?? null) !== $jobName || ($job['ref'] ?? null) !== $defaultBranch) {

tia-baseline is the default. If your job has another name, point Pest at it:

pest()->tia()->baselined(job: 'my-baseline-job');