MergeGuide integrates with GitHub at the PR gate and repository level. Policy violations block merges. Evidence artifacts are generated on every evaluation. The GitHub Actions workflow takes five minutes to set up.
The MergeGuide PR gate runs as a GitHub Actions check on every pull request. It evaluates all changed files against your active policy set and reports results as a required status check.
Branch protection rules are configured to require the MergeGuide check to pass before merge. A PR with compliance violations cannot be merged — period. Not without an approved exception logged in the evidence trail.
Add the MergeGuide GitHub Action to your workflow and configure branch protection rules.
# .github/workflows/mergeguide.yml
name: MergeGuide Compliance Check
on:
pull_request:
branches: [main, develop]
jobs:
compliance:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- name: MergeGuide Policy Check
uses: mergeguide/action@v1
with:
api-key: ${{ secrets.MERGEGUIDE_API_KEY }}
# Optionally override frameworks for this repo
# frameworks: soc2-type2,hipaaThen set MergeGuide as a required status check in your branch protection rules: Settings → Branches → Add rule → Require status checks → Add "MergeGuide Compliance Check".
Install the MergeGuide GitHub App for automatic repository setup, organization-level policy management, and dashboard visibility across all repos.
Organization-wide policy configuration. One mergeguide.yaml in a central repo drives policies across all repositories in the org.
MergeGuide automatically labels PRs with compliance status tags and assigns compliance reviewers based on violation type, using your CODEOWNERS configuration.
Join the waitlist for early access to the GitHub integration and MergeGuide Actions.