FAQ

Frequently asked questions.

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.

Is MergeGuard SOC 2 compliant?

MergeGuard is on a SOC 2 Type II roadmap and operates with security-minded defaults today: scoped GitHub App permissions, TLS for all traffic, managed secrets, and in-memory processing for review jobs. Contact us for security questionnaires, DPAs, and compliance timeline details.

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 support private repos?

Yes. Install the GitHub App on your org or account, or connect a GitLab project from the dashboard.

Does it replace human reviewers?

No. MergeGuard augments your team with risk signals and suggested fixes.

Why didn't @mergeguards fix run?

On GitHub, reply on an inline finding. On GitLab, reply on a Changes tab diff thread—not a top-level Overview note.

Why a new full review after my fix commit?

On GitLab MR update, auto-fix pushes are skipped. Use @mergeguard-followup to re-scan.

GitHub email ≠ MergeGuard login?

Contact support →