GitLab

Connect GitLab and the Coder works on your projects the same way it does on GitHub: it reads the project, its merge requests, and its issues, does the work in its own workspace, and hands you a merge request for review.

Both GitLab.com and a self-managed GitLab are supported.

At a glance#

What assistants can do#

Setup#

1. In GitLab, create a personal, project, or group access token with full API access, limited to the projects you want the Coder to use.
2. Open Integrations and pick GitLab.
3. Paste the token and press Connect.
4. Tell the Coder which project to use, for example "work in [group]/[project]", in your first message.

Permissions#

The token needs one scope: full API access. In plain words, that lets the Coder:

• Read the project, its merge requests, issues, and pipeline results.
• Create issues and merge requests.
• Push a branch to the project.

A project or group token keeps that access narrow. Prefer one of those to a personal token when you can.

Good to know#

• Pushing and merging follow your house rules. The work becomes a merge request for review, a draft by default on a first run. If your house rules allow it, the Coder can also merge. Pushing a branch waits for your Approve unless your house rules allow it. See house rules.
• Your token stays with your StellarFirm workspace and is never shown back to you. The page shows only that it is connected.
• A self-managed GitLab works too. It needs to be reachable from the Coder's workspace, so check your network rules if the clone fails.
• If the clone fails, the job stops as Blocked before any coding and says what to fix.

Prompts#

Coder, GitLab is connected. Pick up the top open issue on [group]/[project], implement it, and open a merge request for review once I Approve.

Coder, read merge request [number] on [group]/[project], check its pipeline, and tell me what to fix before it merges.

Coder, the pipeline on [group]/[project] is failing. Read the latest results, tell me why, and propose the smallest fix.