Allow changes since last review to work with rebased branches

[innomatics]

Select Topic Area

Product Feedback

Body

Our team uses the changes since last review a lot, but it does not work when branches are rebased and force-pushed as the rebased commits are treated as occurring after the last review.

If there was an option to show changes since my last review, but take into account the commit time (which is preserved after rebase), then the reviewers could use this feature to review only the commits since last review, even if the branch has been rebased and force-pushed since the last review. This option could also apply to the conversation stream so that comments appear in the logical historical order in relation to commits.

One workaround is to select multiple commits for review (shift-click in clunky in the UI when a lot of commits need selecting), another is to update the URL directly e.g. pull/123/files/<first-un-reviewed-hash>-..HEAD

A nicer workaround would be 'Show commits since commit X' UI feature.

The workarounds require the reviewer to use command line tools or otherwise to figure out what the first un-reviewed commit was.

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

[sandstrom]

Here is a blog post mentioning this problem:

https://daisy.wtf/writing/github-changes-since-last-review/

Suggesting the use of git range-diff, maybe Github could use that to fix this bug?