GitLab
Sigilix reviews GitLab merge requests with the same engine that reviews GitHub PRs — the same specialists, the same believability gates, one review per MR with inline findings.
Sigilix is live and self-serve — sign up free or start a 14-day Pro trial to connect GitLab. You can also sign in to the dashboard with GitLab directly.
Connect a project
There is no manual webhook or token setup — connecting is one click per project:
Sign in at app.sigilix.ai
Sign in to the Sigilix dashboard — with GitHub or with GitLab.
Open the GitLab connector
In the dashboard, open GitLab from the apps list and click Connect GitLab. You’re taken through GitLab’s standard OAuth authorization and returned to the dashboard.
Pick your projects
The connector lists the GitLab projects where you have Maintainer access or above. Connect each project you want reviewed in one click — Sigilix creates the merge-request webhook and a scoped project access token for you, server-side.
Disconnecting a project reverses the setup: the webhook is removed and the review token revoked.
What happens on a merge request
When an MR is opened or updated on a connected project, the dispatcher routes it into the same review pipeline GitHub PRs use. The review posts as:
- A summary note on the MR — the synthesizer’s verdict and what survived the gates
- Inline discussions per finding, anchored to the lines they cite — resolvable like any GitLab discussion thread
Findings carry the same specialist tags, severity badges, and proof-tier pills as on GitHub. Duplicate webhook deliveries for the same MR head are deduplicated, so you never get two reviews for one push.
Security model
- The webhook secret and the project’s review token are generated and stored server-side — they are never displayed, logged, or handled by you.
- Your Maintainer-level access is re-verified through your own GitLab authorization before a project can be connected.
- A project already connected by another Sigilix workspace is refused — connections are tenant-isolated.
- Reviews address projects by their immutable project ID, so a token can never be steered at a different project than the one you connected.
Current scope
GitLab support is newer than the GitHub integration, and some GitHub-side features are still GitHub-only for now — the deeper PR-thread interactions like @sigilix mentions and slash commands are documented for GitHub. If a GitLab-side capability matters to your team, tell us: support@sigilix.ai.