Safe Pull Request

About

**Avoid Accidental Pull Requests and Protect Your Code**
Working on a forked repo? Stop accidental pull requests to the wrong repo with Safe Pull Request. This extension ensures your PRs target the correct repo, saving you from unwanted code leaks, embarrassing mistakes, and unnecessary spam to upstream maintainers.

**Key Features**
* Default Target Repo: Automatically sets the default pull request target to the current fork, instead of the upstream repository.
* Respects the repo's default branch. No matter if your default branch is named "main" or "develop" or "mr-potato-head", PRs will open against that branch. As they should.
* Code Leak Prevention: Avoid accidentally exposing sensitive or private code to the wrong audience.
* Spam-Free PRs: Prevent spamming upstream maintainers with accidental PRs.
* Supports PRs created from Claude Code! If you use the "Create PR" button in Claude Code, the extension will redirect the GitHub page so it prompts you to open the PR against your fork.

**Who Is This For?**
Safe Pull Request is designed for developers who work with forked repositories and use the GitHub web interface to create pull requests. If you’ve ever accidentally opened a PR against the upstream repo, this extension is for you.

**Why Install Safe Pull Request?**
1. Protect Your Code
* When you accidentally open a pull request against the upstream repo, your code can be exposed to anyone with access to that repo. Even worse, if the upstream repo is public, your code will be visible to the public Internet. Safe Pull Request eliminates this risk by setting to your fork as the default target repo.

2. Save Time and Avoid Embarrassment
* Mistakes happen, but accidental PRs can spam the upstream maintainers. And frankly, accidental PRs are just a bit embarrassing! Safe Pull Request helps save the maintainers' time and save YOU from being fallible. Because you're not. You're perfect.

**Limitations and Known Issues**
* Future Feature: Ability to configure the default target repo on a per-repo basis.
* Known Issue: PRs opened from the /branches page are not currently handled properly, meaning they could target the upstream repo. This will be addressed in the next release.

**Licensing**
Safe Pull Request is free for personal use. However, in order to function on organization repos, it requires a valid license key.

How to Get a License: Visit safepullrequest.com to purchase a license. Then enter the license key in the extension interface.

**How It Works**
Once installed and activated, Safe Pull Request seamlessly integrates into the GitHub web interface. When you open a PR from a forked repository, it ensures the default target is your forked repo.

**Install Now and Code with Confidence**
Eliminate code leaks, avoid upstream spam, and streamline your workflow. Install Safe Pull Request today and never worry about PR mistakes again.

**What data does Safe Pull Request collect?**
We are committed to transparency about data collection. The extension only collects:
* Repository owner names, to check if they are organizations. Not stored, only checked in real-time.
* Your license key and GitHub username, if applicable. Only to validate access and provide support.

We do not:
* Read your source code
* Access private repository data
* Track your browsing history

The extension only modifies GitHub's compare links to protect against accidental upstream pull requests. All license validation happens server-side with minimal data transfer.

For more details, see our privacy policy, which is written in plain English: https://safepullrequest.com/privacy