Unable to review large pull request

[GunterGladDC]

Select Topic Area

Bug

Body

When I have a large pull request I cannot review the changes. The pull has more than 7K files changed and the UI limits to 3K and becomes unresponsive and I cannot use filters. Is there a way to:

• Increase the performance so UI does not "lock up" and become unresponsive.
• Better filtering. We recently migrated from Azure devops and it allowed us to filter by Folder.
• Are there alternative tools to use?

Info on the pull request:

I do understand that "smaller pull requests" is the suggested approach. But, this is not a viable option and we MUST have support for a large number of file changes. We were using Azure devops and this had no problem with the size of the change.

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

[ghostinhershell]

Hi @GunterGlad,

Thanks so much for reaching out in our community. Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views. Those limits are imposed to ensure that the request to generate the page will complete in a reasonable amount of time. You can learn more here: Diff limits.

We recommend making smaller PRs with fewer files and commits to avoid this problem in the future. I understand this might not be the answer you were hoping for. GitHub is always working to improve and expand its functionalities, so this could change in the future.

[GunterGladDC]

Sorry, this is not a great reply. In my question, I specifically said your suggested solution is not an option. So the only option we have is to move back to ADO as GitHub is not a viable option.

[scouzi1966]

Is this resolved? I want to subscribe to the paid service. But If I have to micro manage and break PRs into pieces. Forget it.