Feature request: option to stop defaulting pull requests to upstream fork

[peterwwillis]

Select Topic Area

Product Feedback

Body

I am annoying upstream open source maintainers. I keep opening a pull request in my fork, so I can merge my changes into my fork... but it sort of silently/secretly/automatically points my PR at the upstream repo by default. I forget, and open the PR quickly, and it goes into the upstream repo. Now the upstream maintainer is barraged by my stupid pull requests which aren't supposed to go to him.

This is contributing to the burned-out open source maintainers. Please let me turn this off, so my repo is the one that gets the fork.

Otherwise I will have to clone offline, and push to my own repo without using GitHub's forking feature. This just makes me want to leave GitHub.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐