FAQ
Frequently asked questions
Questions people ask before they install. Setup, security, GitHub vs GitLab, and what happens on a big diff.
Common questions
Open any question. For a walkthrough, see the setup guides or a short demo.
Does MergeGuard support GitLab?
Yes. Sign in with GitLab, pick a project from the dashboard, and reviews land on your merge requests — comments on the diff, a suggested fix, same idea as GitHub.
Does MergeGuard review large PRs?
Yes. Big diffs are where people skip lines. MergeGuard still reads them and flags the risky files so you know where to start. On paid plans you can ask for a deeper pass.
Does MergeGuard support monorepos?
Yes. Install it on the repo (GitHub App or a connected GitLab project). Each PR or merge request is reviewed from its own diff. TypeScript, Python, Go, Java, Ruby, Rust, and more can live in the same repo.
How does MergeGuard compare to CodeRabbit?
Both review GitHub pull requests. MergeGuard is built around a risk score, security in the same comment, and a one-reply fix. CodeRabbit is stronger if you want a chatty PR walkthrough. For a side-by-side, see MergeGuard vs CodeRabbit.
Does MergeGuard read private repos?
Yes. On GitHub you pick which repos the app can see, and you can revoke that anytime. On GitLab you connect the projects you want from the dashboard.
Does it replace human reviewers?
No. You still decide what merges. MergeGuard names the risk, the issue, and a suggested fix so humans can spend time on product and design.
Which languages are supported?
TypeScript, JavaScript, Python, Go, Java, Ruby, Rust, C#, PHP, and more. One review across a mixed repo — not a new tool per language.
How do I sign in to MergeGuard?
On the sign-in page, choose GitHub or GitLab. There is no separate MergeGuard password. Use the same account that installed the app or connected your projects.
How does GitHub work with MergeGuard?
Connect GitHub, install the app on the repos you care about, then open a pull request. MergeGuard posts a summary on Conversation and comments on Files changed. Reply @mergeguards fix on an inline thread to apply a patch, or @mergeguard-followup on Conversation to re-scan.
How does GitLab work with MergeGuard?
Connect GitLab, then pick a project from Dashboard → Connect GitLab project. On each merge request, MergeGuard posts an overview and comments on the Changes tab. Reply @mergeguards fix on a diff thread; use @mergeguard-followup on Overview when you want another full pass.
Why didn’t @mergeguards fix run?
It has to be a reply on the finding itself. On GitHub that’s an inline thread. On GitLab that’s a Changes tab discussion — not a top-level Overview note.
Why did GitLab not run a full review after my auto-fix commit?
On GitLab we skip an automatic re-review after an auto-fix push, so you don’t get a loop of comments. Post @mergeguard-followup on the Overview tab when you want a full re-scan.