Comparing changes no longer shows if conflicts or not

[harwellsa]

Select Topic Area

Bug

Body

As of Friday, 6/13/25, the Comparing changes page is not showing whether there are conflicts or not (after selecting two branches to compare). Was this feature removed or is there a bug?

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

[thinkasany]

This feature is very useful for us. We use master / feature / next to maintain the corresponding patch / minor / major. We often need to resolve conflicts between branches. Whether the conflict is displayed can help us choose to create a merge branch directly or resolve the conflict through next-merge-feature first, and then merge it into next

[nonatoaraujo]

Here we have the same problem, when starting to open a PR it no longer shows the information if there are conflicts.

[ericferreiraefeso]

It's causing a lot of efforts, because we need to open the PR to be checked if it has some conflict. Previously it was possible to view conflicts even before opening the PR, which was much more practical 😅

[harwellsa]

It's unclear why the GitHub team hasn't replied yet. The changelog does not show why it was removed.