Unresolved Conversations Blocking PR Merges Must Be Visible

[excenter]

Select Topic Area

Bug

Body

Issue:
When attempting to merge a pull request, GitHub sometimes blocks the merge with the message “conversations must be resolved.” However, there are cases where unresolved conversations are not visible or easily discoverable in the UI, making it difficult or even impossible for users to resolve them and proceed with the merge.

Impact:
This can disrupt development workflows, create confusion, and lead to unnecessary delays in merging PRs.

Request:
If unresolved conversations are blocking a PR from merging, GitHub should ensure that these conversations are:

• Easily accessible from both the “Conversation” and “Files changed” tabs
• Never hidden, outdated, or suppressed in a way that prevents users from finding and resolving them

Benefit:
This would improve developer experience, reduce friction in the review process, and help teams maintain momentum in their workflows.

Thank you for considering this improvement!

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

[excenter]

Alternatively, if a comment is outdated enough that it doesn't show up in the UI, it shouldn't block a merge.