See MergeGuard on a real GitLab merge request

Connect GitLab, open a merge request, and watch the review land on Overview and the Changes tab. Same idea as GitHub — comments on the diff, a suggested fix.

Setup guide GitHub demo →

GitLab walkthrough video

From install or connect through review summary, changes inline comments, and MR commands.

youtube.com — GitLab MR walkthrough

What it looks like on GitLab

Overview first, then comments on the diff. Your team stays in GitLab.

GitLab merge request Overview tab with MergeGuard review note showing risk score, severity counts, recommended fixes, and link to inline findings on Changes — Overview note first: risk score, **Recommended fixes**, then per-file findings. Open **Changes** for threaded inline comments.

GitLab merge request Changes tab with MergeGuard high-severity inline security comment on newapi.ts and @mergeguards fix prompt — Findings on the **Changes** diff—reply **`@mergeguards fix`** on the thread to apply a patch on the MR branch.

GitLab merge request thread showing @mergeguards fix command and MergeGuard confirmation that an auto-fix was committed to feat-api — MergeGuard commits to your source branch and replies in the same discussion with what changed.

GitLab merge request Overview with MergeGuard deep scan summary showing elevated risk score and recommended fixes — Post **`@mergeguards deep-scan`** on the MR **Overview** tab for a heavier security and architecture pass (paid plan).

Try it on your GitLab project

Sign in with GitLab, connect a project, open an MR. The first review usually shows up within a minute. Reply on the Changes tab for a fix; use Overview when you want another full pass.

GitLab quickstart View pricing GitHub demo

← All demos·GitLab integration·GitHub demo

GitLab product demo