Docs/NOME Build Cloud/Connect GitLab

Connect GitLab

Authorize the GitLab connector, ingest merge-request events, and post commit statuses back to GitLab.

Authorize the connector

Connect a GitLab project or group through the NOME connector OAuth flow. The owner token is resolved from the connector vault, used to post commit statuses, and never logged. NOME fails closed when no token is connected — it skips with a clear reason rather than guessing.

Inbound events

NOME ingests GitLab merge-request webhook events on open, update, and reopen, plus push events, and opens or updates runs against a canonical work item. The AI review prompt is built from the merge-request diff.

Commit status post-back

Build, test, and review results are posted back as GitLab commit statuses with a stable context name (for example nome-ci or nome-ci/<job>) so GitLab replaces a status rather than stacking duplicates. A review verdict can post under its own context (for example nome-review) so it shows alongside the CI status. Statuses map cleanly: pending, running, success, failed, canceled, skipped.

Bring your own YAML

Your .gitlab-ci.yml stays in your project. NOME reads it and runs the stages on the runner you select — owner-edge or NOME cloud. Branch naming and merge-request conventions are yours; NOME extends them rather than replacing them. No lock-in.

Ready to try it?

Open NOME