Feature: Multiple PR templates that auto-display based off the upstream branch name

[PureKrome]

Select Topic Area

Product Feedback

Body

Simple Feature Request

The PR template to show is based off the upstream branch (which you wish to merge your PR into). If there is no file named after the upstream branch, then it defaults to the current logic of using pull_request_template.md

Details/Discussion

The current process is that GH does offer limit functionality for multiple PR's. This is NOT AUTOMATIC though - it's via a silly 'query string hack'. As far as I'm aware no one will ever manually update their PR url to include the querystring options. I would assume that most people just create a normal pull request and all the existing tools don't set the template querystring.

INSTEAD we can make this really easy, for teams and organisations.
Similar to the existing documentation, we can have multiple markdown files in the PULL_REQUEST_TEMPLATE folder. Each file (minus the '.md' extension) is the name of the branch you wish to PR your code into. If there's no file which matches the branch GH then falls back to the current rules which is to use the PULL_REQUEST_TEMPLATE.md file if that exists.

For example:

• Source: My fork/branch = origin/fancy-pants-feature
• Destination: Upstream repo, 'dev' branch: upstream/dev
• Upstream repo has the following structure:

So yeah - hope GH, you might consider this feature please.

[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. ⭐

[jakeatoms]

This needs to happen in some form. I would take it a step further and allow specifying a template in the applicable Ruleset.