Render force-push compare diff inline in the PR conversation, not as a separate page

[goelakash]

🏷️ Discussion Type

Product Feedback

Body

Summary

When a contributor force-pushes to a PR branch, GitHub adds a timeline entry like:

goelakash force-pushed the my-branch branch from 8139a28 to ef78ad8

The hash range links to a separate /compare/<old>..<new> page, which navigates the reviewer away from the PR. Reviewing what changed between iterations requires opening it in a new tab and context-switching back to the PR.

Request

Make the compare diff render inline as a collapsible/toggleable section within the PR conversation timeline, similar to how review comments show diff context inline.

Why this matters

The current friction is one of the main reasons maintainers ask contributors to push incremental commits instead of force-pushing clean revisions. If reviewing force-push iterations were as easy as expanding a section in the conversation, more projects could allow contributors to maintain clean commit histories during review.

Example

Today:

• Click 8139a28...ef78ad8 → navigates to a separate compare page

Proposed:

• Click 8139a28...ef78ad8 → expands an inline diff view inside the PR conversation, collapsible like outdated review comments

Related

• Improve workflow when force-pushing during code reviews #3478 covers the broader force-push workflow problem; this is a specific UX proposal to address part of it.

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