Codebase Context #161942
Replies: 2 comments
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Yeah, I’ve had the same thought ever since I tried out Cursor. The way it understands the whole codebase /functions, types, relationships between files, it just feels like it gets what you're trying to do. With Copilot inside VS Code, it’s still impressive, but it’s mostly focused on your current file or the ones you've opened recently. Which is great for boilerplate or simple patterns… but once you’re working in a large repo with multiple layers, it starts falling short. I actually dug into Copilot View recently turns out GitHub has already been exploring exactly this. It's called “Copilot for Your Codebase,” and the idea is to make Copilot act more like a teammate that’s familiar with your whole project, not just a glorified autocomplete. They’ve built something like a retriever system — it indexes your codebase and pulls in the most relevant files/snippets based on what you're working on. So if you're editing It’s still experimental, but the foundation is there. Honestly, it makes Copilot feel way more intelligent like it’s actually collaborating instead of guessing. What does the community need to do to get this into the main product? I think we need to keep asking for it. Feature request it. Upvote it. Show GitHub that devs working on real-world, messy codebases need this level of context to trust AI suggestions. Because yeah Copilot is powerful, but until it sees the whole picture, it's like pair programming with someone who’s only skimmed the README. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
VS Code
Body
I had a chance to test Cursor IDE and i dont understand why github havent allowed copilot to have that kind of codebase context. Copilot is great but if it can go through my whole codebase and understand the structure, features and functionalities it will be super useful. what does the community need to do to achieve this?
Beta Was this translation helpful? Give feedback.
All reactions