Branch Guard installs statistics

BranchGuard runs configurable checks on pull requests based on which files changed. Define rules in a YAML config file with no CI pipelines required. Enforce migration sync, lockfile consistency, team approvals and more.

BranchGuard is a GitHub App that enforces programmable branch protection rules on pull requests. It evaluates conditions using the GitHub API and posts pass/fail check runs — no CI runner needed.

How it works

Add a .github/branch-guard.yml file to your repository. Each rule specifies which branches and file patterns to watch, and what check to run. BranchGuard evaluates rules automatically when PRs are opened, updated, or reviewed.

Check types

• file_presence — Ensure files on the base branch also exist on the PR branch. Catch missing migrations, diverged protobuf files, or deleted config. • file_pair — When one file changes, require a companion file to change too. Enforce lockfile updates alongside package.json or schema changes alongside migrations. • external_status — Make other check runs conditionally required. Only require frontend lint when frontend files change. • branch_age — Fail PRs from branches that diverged more than N days ago. Keep branches fresh. • approval_gate — Require approving reviews from specific teams or users when certain files change. Like CODEOWNERS, but per-rule and configurable.

Features

• YAML config — all rules defined in .github/branch-guard.yml • PR notifications — sticky comment on failures so authors are notified (GitHub doesn't notify for third-party check failures) • Recheck command — comment /recheck to re-evaluate all rules • Auto-request reviewers — automatically request missing reviewers when approval gates fail • PR body allowlist — authors can acknowledge intentional file deletions with a reason • Branch protection compatible — always creates check runs so rules can be marked as required status checks • Installation backfill — automatically evaluates existing open PRs when first installed • Stateless and lightweight — no database, no external dependencies. All state comes from the GitHub API and your config file.

Description from the GitHub Marketplace listing.