3 items
Makes GitHub compare/pull request links on your forks point at your own repository instead of upstream. GitHub assumes every fork exists to contribute upstream. Its Contribute menu, Compare & pull request banner, and N commits ahead link therefore open comparisons against the upstream repository. That is useful when you are contributing back. It is wrong when your fork has its own default branch and pull requests. GitHub Fork Compare Fix changes this only in repositories you enable: • Compare and pull request links stay inside your fork and use its default branch as the base. • The branch info bar and Contribute menu show commit counts against your fork's default branch. • The N commits behind link still points upstream, where it belongs. • An optional redirect catches upstream compare pages after you open them. • Enable one repository from the toolbar, or manage owner/repo and owner/* patterns in the options page. Repositories you do not enable keep GitHub's usual behavior, so forks used for upstream contributions are unaffected. Privacy The extension has no telemetry and asks for no separate account or API token. It runs only on github.com. Requests go only to GitHub through your existing session. Your list of enabled repositories stays in browser extension storage. Source code under GPL-3.0: https://github.com/D3SOX/gh-fork-compare-fix
Aug 20, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.