Critical regression in Copilot's file reading capabilities and solution quality

[coderpp01]

Select Topic Area

Product Feedback

Body

Feedback:

I've noticed a significant regression in GitHub Copilot's performance after a recent update. The change to reading files in chunks rather than all at once has severely impacted both the speed and quality of assistance.

Specific issues:

1. File reading now takes an excessive amount of time (30+ minutes in some cases) to gather context that was previously available almost instantly
2. Due to the fragmented context gathering, Copilot produces significantly lower quality solutions
3. In a recent session, after spending over 30 minutes reading my Flutter codebase, Copilot produced a "fix" that introduced 18 Dart errors, 14 warnings, and 5 hints

The previous implementation, which could read entire files at once, provided both better speed and more coherent solutions since it had full context of the codebase. The current chunked reading approach has effectively made Copilot much less useful for complex projects.

I understand the need to handle very large files, but this implementation has severely degraded the user experience. Please consider reverting to the previous approach or implementing a more efficient solution that doesn't compromise on both speed and quality.

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