GitHub PR Merge Strategy Restrictor

Name: GitHub PR Merge Strategy Restrictor
Rating: 4.67 (3 reviews)
Author: sharmadhiraj

Control GitHub PR merge strategies based on source and destination branches, and repository.

As of June 2026, GitHub PR Merge Strategy Restrictor has 67 users and a 4.67/5 rating from 3 reviews in the Developer Tools category.

sharmadhiraj Developer Tools

Chrome Web Store ↗.crx

Users−8.2%

Rating0%

4.67

3 reviews

Reviews0%

Version

1.0.5

Manifest V3

History

7 snapshots

Tracking since Apr 11, 2026.

View as table

Date	Users	Rating	Reviews	Version
Apr 11, 2026	73	4.67	3	1.0.5
Apr 21, 2026	68	4.67	3	1.0.5
Apr 26, 2026	68	4.67	3	1.0.5
May 3, 2026	66	4.67	3	1.0.5
May 9, 2026	65	4.67	3	1.0.5
May 20, 2026	67	4.67	3	1.0.5
May 27, 2026	69	4.67	3	1.0.5
Now	67	4.67	3	1.0.5

Permissions & access

Permissions: storage
Host access: None declared

Screenshots

GitHub PR Merge Strategy Restrictor screenshot 1

GitHub PR Merge Strategy Restrictor screenshot 2

About

This extension helps you control GitHub PR merge strategies based on source and destination branches and repos. Since GitHub doesn't support this feature, I built it to prevent mistakes, like using the wrong merge strategy. For example, I squash all merges except when merging to master, but sometimes I make a mistake in the flow. This extension ensures that doesn't happen. You can define rules with exact branch names, wildcards, or patterns, making it flexible for different scenarios.

Example Restriction Rules:
- You can specify exact names for the repository and branches.
- Use * to apply the rule to all repositories or branches.
- Use wildcards like company-name/* to match all repositories starting with 'company-name' or feature/* for all branches starting with 'feature/'.
- You can combine these options, such as using * for the repository, an exact name for the source branch, and a wildcard for the destination branch, or any combination of these.