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

This would be an extremely valuable feature for OSS maintainers and large collaborative repositories.

Right now GitHub only supports automatically closing issues through keywords like:

• Closes #123
• Fixes #123

But there’s no equivalent workflow for pull requests, even though duplicate or replacement PRs are very common in active repositories.

A native feature like:

• Closes PR #123
• Supersedes PR #123
• or selectable related PRs inside the Development section

would improve maintainability a lot.

Some very common real-world scenarios:

• Multiple contributors implement the same feature differently
• A newer PR replaces an abandoned/stale PR
• A maintainer chooses one implementation among several alternatives
• Security or architecture changes make older PRs obsolete
• Refactored implementations supersede previous work

Currently maintainers have to manually:

• close PRs
• explain why
• reference the replacement PR
• update labels/projects
• notify contributors

This becomes repetitive very quickly in medium and large OSS projects.

It would also be helpful if GitHub supported different close states, for example:

• Closed as duplicate
• Superseded by PR #X
• Replaced by newer implementation
• Archived/stale replacement
• Closed after merge of related PR

Additional useful behavior could include:

• automatic cross-linking
• maintainer confirmation before closing
• preserving review history visibility
• optional contributor notification
• timeline events showing which merged PR caused closure

This feature would fit naturally alongside GitHub’s existing issue-closing workflow and would make repository management significantly cleaner and more scalable for maintainers.