Pull Requests should list which GitHub Release(s) reference the PR

[jasonkarns]

Select Topic Area

Product Feedback

Body

Pull Requests note when that PR is referenced by an Issue, another PR, or a commit (whenever the PR number is included in the pr/issue description, or pr/issue comments, or commit message).

These references should be expanded to include Release notes. It is extremely common to need to trace a PR back to see which release it was included in. This is only presently possible by viewing the actual commit page and looking at the myriad tags that can reach the commit. (This is a decent workaround but could be much better. For one, that flow is problematic when using github's squash-merge or rebase-merge flows, as it also breaks git tag --contains. It requires first stepping away from the PR and over to the actual merge commit. And secondly, on the commit page it shows all tags (releases) that can reach that commit. Which grows unwieldy extremely fast.)

An improvement to this (not wholly a replacement), would be to extend the "PR # referenced by" linkbacks in the PR view to also capture when a Release references the PR. This would drastically improve the tracing from an Issue and PR to the release that ships said Issue/PR.

It's already the default behavior for github's Release to capture PRs included in the release, thankfully. The improvement would be that only a single Release (and thus only a single tag) would reference the PR in the common case. Therefore there won't be an explosion in "tags this commit is included in" as exists on the commit page.

To summarize: Having a "Released in {link to release}" annotation on the PR page that points to the GH Release that includes (references) the given PR would make it much easier to trace from a PR to the git-tag that first includes said PR.

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