Load diff button on PR files changed should be visually distinct for large diffs vs generated

[kirk-anchor]

Select Topic Area

Product Feedback

Body

When performing a code review, the files changed tab will hide the contents of a file behind a Load diff button if the diff is large or if it's marked as a generated file in a .gitattributes file.

The problem is the Load diff button looks the same in both cases and the only way to determine why the contents were not rendered is the small text underneath the Load diff button having either:

Large diffs are not rendered by default.

or

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

I almost never want to review the generated files because in my code, they are generated deterministically and have automatic validation. However I always want to review large diffs because they are often the most important changes in the particular PR. The lack of visual distinction on the Load diff button depending on if they were generated files vs large diffs makes it easy to miss reviewing a large diff when performing a code review.

Example screenshot

Even a small change like making Load diff a different color such as gray for the generated file so that it's visually distinct from the blue Load diff on the large diff would make it a much better experience when reviewing a large PR.

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