Stop Accidental PRs to Upstream Repos
Forked a repo? The Safe Pull Request browser extension ensures your pull requests go where they're supposed to: your repo, not upstream.
Upstream PRs are leaking your code
When you open a PR against the wrong repo, you are leaking your code to everyone who has access to that repo. And notifying all the followers. 🤦
Safe Pull Request eliminates this risk by defaulting to your repo.
Pricing
Personal
Free
Just install the Chrome extension
- PRs open against your repo
- Works with personal repositories
While supplies last
Professional
$10
$6.50/month
- PRs open against your repo
- Works with personal repositories
- Works with organization repositories
Go ahead, expense it
Already bought a license key?
Next step...
Frequently Asked Questions
+ How do I change the default base repository for my GitHub fork?
Short answer: Install the Safe Pull Request extension.
GitHub doesn't yet provide a built-in setting to change the default base repository for pull requests. By default, GitHub always targets the upstream (original) repository when you create a pull request from a fork.
Safe Pull Request solves this problem automatically. Once installed, the extension changes the default base repository to your fork. That way, when you open a PR from your fork, it will be a PR against your fork.
+ How does Safe Pull Request work?
The extension modifies GitHub's compare links to open PRs against the current repo, not the upstream repo.
It also makes an API call to GitHub to find out if a repo's owner is an organization or an individual. If the owner is an organization, then the extension requires a Professional license before it modifies GitHub's compare links.
+ What data does Safe Pull Request collect?
We are committed to transparency about data collection. Here's exactly what we collect.
Chrome Extension
Collects the following data:- Repository owner names (to check if they are organizations)
- Your license key (to validate access)
- Your GitHub username (to prevent license key sharing)
The extension does NOT:
- Read your source code
- Access private repository data, other than fetching the name of your default branch so the extension knows which branch to open PRs against. This is not stored.
This Website
Collects the following anonymous data:- Page view counts and navigation patterns
- Button clicks ("Install Extension", "Buy License")
- Marketing campaign sources (if you visited this page via a marketing campaign link)
Important: Our website analytics is cookieless - no cookies or persistent tracking across sessions.
The website does NOT:
- Track your browsing history outside our website
- Store cookies or persistent identifiers
- Track you across other websites
+ Does Safe Pull Request read my source code?
No, Safe Pull Request does not read your source code.
+ Why do my pull requests go to the wrong repository?
If you're working with a forked repository, GitHub defaults to targeting the upstream (original) repository for pull requests, not your fork. This default behavior is nice for open source contributions, but it causes problems when:
- The upstream repository is archived or abandoned
- You're using the fork for your own development
- You want to keep your work separate from the original project
- The upstream maintainers don't accept pull requests
Safe Pull Request fixes this by automatically changing the default base repository to your fork, so you stop accidentally opening PRs against the wrong repo.
+ How can I prevent accidental pull requests to upstream repositories?
Accidentally creating pull requests to upstream repositories is a common problem when working with GitHub forks. The only reliable way to prevent this is to change the default base repository behavior.
Unfortunately, GitHub doesn't yet provide a built-in setting to change this, but Safe Pull Request provides an automated solution: it modifies GitHub's PR behavior to default to your fork as the base repo instead of the upstream repository.
+ If I install Safe Pull Request, can I still open a PR against an upstream repo from my fork?
Yes! On the "Open a pull request" page, simply click the "compare against forks" link.
Then, in the "base repository" dropdown, select the repo you want to open the PR against.