GitLab

Connect a GitLab group so Polylane reads its code, reviews its merge requests, opens merge requests with fixes, and links each project to the resources it deploys. One connection covers one group and all of its subgroups.

GitLab.com

1. Click Connect GitLab, then Continue with GitLab.com.
2. Sign in as an Owner of a top-level group and approve the Polylane application.
3. Choose the group. Groups on the Free plan are not available, because group webhooks need GitLab Premium or Ultimate. Trials of either plan work.
4. Polylane adds a service account to the group with the Maintainer role, gives it a token, and adds a group webhook. It then revokes the sign-in grant.

Polylane acts as the service account from then on, so its activity in GitLab shows under that account, not under your name.

Self-managed GitLab

1. In the group, open Settings > Access tokens and create a group access token with the Owner role and the api scope. A service account token with the same access also works.
2. In Polylane, click Connect GitLab and enter the instance URL and the token.
3. Click Find groups, choose the group, and click Connect group.

The instance must be reachable from the public internet with a valid TLS certificate.

What Polylane does in the group

• Merge request reviews. When a merge request to the default branch opens, gets new commits, or leaves draft, Polylane assesses it against the live infrastructure. It writes one summary note that it updates on each run, adds discussions on the changed lines that need attention, and sets a commit status. Write @polylane in a note to run the review again.
• Fixes. Polylane opens merge requests with fixes from the service account, on branches that start with polylane/. A note on one of these merge requests starts a follow-up change, and Polylane reacts with 👀 when it gets the note. When a pipeline fails on one of these merge requests, Polylane reads the job logs and pushes a fix.
• First merge request. When you connect, Polylane opens one merge request that adds a Polylane section to AGENTS.md, so that coding agents in the project know how to use Polylane.
• Pipelines. Polylane raises an issue when a pipeline fails on the default branch. It also watches the pipeline failure rate, duration and queue time for anomalies.

What Polylane keeps up to date

• New, renamed, moved and removed projects follow within seconds through the group webhook, and a daily resync corrects anything a delivery missed.
• A push to a project's default branch refreshes that project and its links to deployed resources.
• Once a day, Polylane checks the group webhook. GitLab turns a webhook off after failed deliveries. If the connection token can manage webhooks, Polylane turns the webhook on again, or creates it again if it was deleted. If Polylane cannot fix it, it tells the workspace owners and admins what to do.
• Polylane renews the service account token it creates before it expires. A token you paste stays yours: renew it in GitLab before it expires, then connect again with the new token.

Permissions

When you disconnect, Polylane revokes its service account token. The service account and the group webhook stay in the group until a group Owner removes them.