AI code review for GitLab merge requests
Solemly reviews GitLab.com merge requests through an access token you connect once. Each review is one note on the merge request listing every finding with its file, line and severity, and the result is reported as Solemly / Review, Solemly / Security and Solemly / Summary commit statuses on the merge request's pipeline.
Checked against the product on 2026-11-03.
What a review posts on GitLab
- One note on the merge request per review, with the summary followed by every finding and its file, line and severity.
- Commit statuses:
Solemly / Review,Solemly / Security,Solemly / Summaryand, with Jira connected,Solemly / Acceptance. - Replies to
@solemlycommands, such as@solemly reviewor@solemly ask.
GitLab doesn't get inline comments yet. Findings are listed in the review note with their file and line.
Who the reviews appear from
Solemly posts reviews, replies and commit statuses as the user who owns the token, so pick the token accordingly.
| Option | GitLab plan | Reviews appear as |
|---|---|---|
| Group access token (recommended) | Premium or Ultimate | A bot user for the group |
Dedicated bot account, such as solemly-bot | Any plan, including Free | That account, added to your group as Maintainer |
| Your personal token | Any plan | You |
Connect GitLab
- Create a token with the
apiscope and the Maintainer or Owner role. - In Solemly, open Repositories, choose GitLab, paste the token and click Test & connect. Only workspace admins can connect a code host.
You don't set up webhooks yourself. Solemly lists every project the token's user is a member of, registers a group webhook on each top-level group where the token has Maintainer access or higher, and a project webhook on each project it can manage. New projects in those groups are picked up automatically when their first merge request or comment arrives.
Block a merge request
Turn on Block on high severity for the project in Solemly, and the Solemly / Review commit status fails on any CRITICAL or HIGH finding. Then, under Settings → Merge requests → Merge checks in GitLab, turn on Pipelines must succeed, so the failed status blocks the merge. A fix pushed to the branch gets a new review, and the status passes when nothing high-severity is left. See Block a merge on AI code review findings.
What's supported
Solemly connects to GitLab.com. Self-managed GitLab isn't supported yet.
Questions
Does Solemly support self-managed GitLab?
Not yet. Solemly connects to GitLab.com; self-managed GitLab isn't supported yet.
Do I have to set up webhooks?
No. When you connect, Solemly registers a group webhook on each top-level group where the token has Maintainer access or higher, and a project webhook on each project it can manage.
Who do the reviews appear from?
The user who owns the token: a bot user for the group with a group access token (GitLab Premium or Ultimate), a dedicated bot account such as solemly-bot added to the group as Maintainer on any plan, or you with a personal token.
How do I block a merge on GitLab?
Turn on Block on high severity for the project in Solemly, then turn on Pipelines must succeed under Settings → Merge requests → Merge checks in GitLab, so a failed Solemly / Review status blocks the merge.
In the docs
Related
Try it on your next pull request
Free for 14 days with every feature, no credit card. Install it on a repository and the next pull request gets reviewed.