Improve Pull Request File View by Allowing Hierarchical Folder Grouping

[Hemaravishankar-tirumalla]

Select Topic Area

Product Feedback

Body

When raising a pull request, the “Files changed” tab shows all modified files in a flat list. For large PRs, especially ones with changes across multiple modules or nested folders, reviewers often find it difficult to understand the code structure at a glance.

Feature Request:
Introduce an option to view changed files grouped by project folder hierarchy. This would allow reviewers to expand/collapse directories (similar to the repository file tree), making it much easier to understand the organization of the changes and navigate through them efficiently.

Why this helps:

• Clear visibility into module-wise changes
• Faster understanding of code structure
• Better review experience for large PRs
• Reduces cognitive load for reviewers
• This enhancement would significantly improve code review workflows for teams working on complex repositories.

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