Squash Guard

Disables "Squash and merge" on GitHub PRs that target protected branches (e.g. qa, staging, main).

Squash Guard stops accidental squash merges into the branches where you need to keep full commit history. WHY THIS EXISTS GitHub lets you require linear history, which blocks merge commits, but it has no simple built-in way to block only "Squash and merge" on selected branches. The only native option is turning squash merging off for the whole repository, which also breaks your feature-branch workflow. Squash Guard fills that gap in your browser. WHAT IT DOES When you open a pull request whose base branch is on your protected list, the "Squash and merge" button and its dropdown entry are greyed out and cannot be clicked. A tooltip explains why. Pull requests into any other branch are not affected, so you can still squash into development as usual. FEATURES • Choose your protected branches (default: qa, staging, main) • Limit it to specific GitHub orgs (my-org) or single repos (my-org/my-repo), or apply it everywhere • Works with GitHub's dynamic page loading, so it keeps working as you navigate between pull requests • Light and dark mode settings page • No account, no tracking, no network requests HOW TO USE Open the extension's Options page, enter your protected branches separated by commas, optionally add orgs or repos, and click Save. Changes apply immediately to open pull request tabs. PRIVACY Squash Guard runs only on github.com pull request pages. It reads the PR's base branch from the page and stores your settings locally in your browser. It collects, transmits and sells no data. NOTE This is a convenience guard in your browser UI, not a server-sit stop merges made through the GitHub API, the CLI or anotherbrowser. If you find it useful, you can support it on Ko-fi: https://ko-fi.com/sushantgulati