English (United States)
See more
Stop making accidental pull requests against the upstream repo of your fork.
Latest Version
Version
0.0.1
Update
December 15, 2024
Size
13.7KiB
Developer
safepullrequest.com
Category
Users
0 
Rating
0 ★
Manifest Version
3
Web Store Status
Extension ID
Languages Support
Permissions
ActiveTab
Storage
See more
Storage
Safe Pull Request Extension
**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.
* Code Leak Prevention: Avoid accidentally exposing sensitive or private code to the wrong audience.
* Spam-Free PRs: Prevent spamming upstream maintainers with accidental PRs.
**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 requires a valid license key to activate. Different types of licenses are available depending on your use case.
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.
Read more
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.
* Code Leak Prevention: Avoid accidentally exposing sensitive or private code to the wrong audience.
* Spam-Free PRs: Prevent spamming upstream maintainers with accidental PRs.
**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 requires a valid license key to activate. Different types of licenses are available depending on your use case.
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.
Source Manifest.json
{"update_url": "https://clients2.google.com/service/update2/crx", "manifest_version": 3, "name": "Safe Pull Request", "short_name": "Safe PR", "version": "0.0.1", "description": "Stop making accidental pull requests against the upstream repo of your fork.", "permissions": [ "activeTab", "storage" ], "background": { "service_worker": "background.js" }, "content_scripts": [ { "matches": [ "*://github.com/*" ], "js": [ "content.js" ] } ], "action": { "default_popup": "popup.html" }, "icons": { "48": "icon48.png", "128": "icon128.png" }, "homepage_url": "https://safepullrequest.com/", "host_permissions": [ "https://api.safepullrequest.com/*" ]}
Read more
