Cooling signalUnknownMedium-risk permissions
GitHub PR Merge Strategy Restrictor icon

GitHub PR Merge Strategy Restrictor

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

Users61Current public install base
Rating4.7Store average score
Reviews3Public review volume
Manifest versionV3Extension platform version
7-day growth-3Net users gained this week
7-day growth rate-4.69%Relative weekly velocity
Preview

GitHub PR Merge Strategy Restrictor Media preview

2 assets
Trend

30-day user trend

Review user movement over the last 30 days.

User Growth Over Time

61616262622026年6月21日2026年6月24日2026年6月27日Latest: 61
Rating trend

30-day rating change

Track rating movement over time to see whether quality signals remain stable.

30-day rating change

Start
4.67
Latest
4.67
30-day rating change
0.00
4.574.624.674.724.772026年6月21日2026年6月24日2026年6月27日Latest: 4.67
2026年6月21日2026年6月27日
Growth overview

Daily, weekly, and monthly growth

Compare 1-day, 7-day, and 30-day net growth and growth rate.

1-day growthFlat
00%
7-day growthDeclining
-3-4.69%
30-day growthDeclining
-6-8.96%
Technical snapshot

Version, languages, and crawl freshness

Review publication date, version, supported languages, and crawl timestamps.

Version1.0.5
ManifestV3
Size67.84KiB
Languages1English (United States)
Published
Store updated
Last crawled
English (United States)
Overview

Product summary

Review the store description, core capabilities, and common use cases.

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.

Reviews

Recent review snapshot

Inspect the latest comments and rating distribution.

The Chrome Web Store shows 3 reviews, but only 0 review bodies have synced into ExtScope so far. Showing the synced reviews available right now.

5
0
4
0
3
0
2
0
1
0