Skip to main content
The PR gate evaluates each pull request against your policies and posts the results back to the pull request. When blocking findings exist, the merge is held until they’re resolved — so policy is enforced consistently no matter who (or what) wrote the code. MergeGuide supports the PR gate on all four major source-control platforms:
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps

​
How it works

When a pull request is opened or updated, MergeGuide evaluates the changed code and reports a status on the PR:
  1. The change is checked against your active policies.
  2. Findings are posted inline on the PR with remediation guidance.
  3. A PR status reflects the result. If there are blocking findings, the merge is blocked until they’re resolved or suppressed with justification.
The specific connection steps differ per platform (app installation, project access, and webhook setup). Follow the guide for your SCM:

GitHub

Connect the GitHub app and enable the PR gate.

GitLab

Connect GitLab and enable merge-request checks.

Bitbucket

Connect Bitbucket and enable PR checks.

Azure DevOps

Connect Azure DevOps and enable PR checks.

​
Make the gate enforce

Reporting status is only half the value — to block merges on blocking findings, enable branch protection (or its equivalent) on your platform and require the MergeGuide status to pass. See your platform’s integration guide and CI/CD patterns.

​
Next steps

Configure thresholds

Decide what severity blocks a merge.

Enforcement layers

How the PR gate fits with earlier checks.