Some more insights - a new feature (currently in preview) helping set the context right for future interactions with Copilot... it's called "GitHub Copilot Spaces":
Distributed backend specialist. Perfectly happy playing second fiddle—it means I get to chase fun ideas, dodge meetings, and break things no one told me to touch, all without anyone questioning it. 😇
Thanks for adding this! I briefly played with the Copilot Spaces feature when it first came out but I have 2 major problems with it (as of a few weeks ago, anyway):
The idea is fantastic and I immediately thought of at least 3 things this would have been perfect for, except every single one I tried ran out of space before I got through the first repo. I was trying hard to limit context to only absolute necessities, too!
Every single chat prompt you send in a copilot space counts as a premium request. I'm already at 36% as of the 4th (to be fair, a good 10% was hack time) and overages aren't an option for me. Makes the fun stuff like this difficult to justify.
The suggestion/workaround copilot made regarding space was for me to rewrite a sort of mock interface instead of attaching the actual class implementation. Which really defeats the purpose, in my opinion. To be honest, I was already on personal time just to pick out relevant files - rewriting them entirely for this single use case isn't happening.
Then GitHub compounds the problem by throwing premium usage on top of that. I'm not the only one at my company who's ran into these issues either. It's one of those things I really want to love, but it's making it really hard for me in an enterprise setting.
I'd love to hear your thoughts though! Have you had success with it? How did it work out once everything was put together?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Some more insights - a new feature (currently in preview) helping set the context right for future interactions with Copilot... it's called "GitHub Copilot Spaces":
github.blog/ai-and-ml/github-copil...
Thanks for adding this! I briefly played with the Copilot Spaces feature when it first came out but I have 2 major problems with it (as of a few weeks ago, anyway):
The suggestion/workaround copilot made regarding space was for me to rewrite a sort of mock interface instead of attaching the actual class implementation. Which really defeats the purpose, in my opinion. To be honest, I was already on personal time just to pick out relevant files - rewriting them entirely for this single use case isn't happening.
Then GitHub compounds the problem by throwing premium usage on top of that. I'm not the only one at my company who's ran into these issues either. It's one of those things I really want to love, but it's making it really hard for me in an enterprise setting.
I'd love to hear your thoughts though! Have you had success with it? How did it work out once everything was put together?