FAQ
Frequently asked questions
GitHub App install, GitLab project connect, security, pricing context, and day-to-day PR/MR commands—everything teams ask before rolling MergeGuard out.
Common questions
Expand any item for details. For setup walkthroughs, see integration guides and product demos.
Does MergeGuard support GitLab?
Yes. Sign in with GitLab OAuth, connect projects from your dashboard, and get automated merge request reviews with inline findings and @mergeguards fix on Changes tab threads—the same command model as GitHub.
Does MergeGuard review large PRs?
Yes. MergeGuard analyzes large pull requests and merge requests, surfaces high-risk file and size signals in the risk score, and recommends @mergeguards deep-scan on paid plans when a diff needs a deeper pass.
Does MergeGuard support monorepos?
Yes. Install on a monorepo repository (GitHub App or connected GitLab project) and reviews run on each PR/MR diff. MergeGuard supports TypeScript, JavaScript, Python, Go, Java, Ruby, Rust, and other languages in the same repo.
How does MergeGuard compare to CodeRabbit?
Both review GitHub pull requests with AI. MergeGuard emphasizes merge risk scores, security-oriented deep-scan, and @mergeguards fix commits from inline threads. CodeRabbit is known for rich PR conversation and summaries. See our MergeGuard vs CodeRabbit and best AI PR review tools pages for a full comparison.
Does MergeGuard read private repos?
Yes. MergeGuard supports private repositories via the official GitHub App with scoped, revocable permissions, and private GitLab projects you connect from the dashboard.
Does it replace human reviewers?
No. MergeGuard augments your team—it surfaces risks and suggested fixes so humans focus on product intent and design.
Which languages are supported?
TypeScript, JavaScript, Python, Go, Java, Ruby, Rust, C#, PHP, and more—ideal for monorepos and polyglot services.
My GitHub email isn’t the same as my MergeGuard login
Sign in with your MergeGuard email and password, then Continue with GitHub on the sign-in page in the same tab. You can also link the installation id from your Dashboard.
Why didn’t @mergeguards fix run?
On GitHub, reply on an inline finding thread. On GitLab, reply on a Changes tab diff thread—not a top-level Overview note only.
Why did GitLab run a full review after my auto-fix commit?
On GitLab MR update, auto-fix pushes are skipped for automatic re-review. Post @mergeguard-followup on the MR Overview tab when you want a full re-scan.