Github copilot coding agent does not use defined codespaces #161180
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, it is really weird that https://docs.github.com/en/copilot/how-tos/agents/copilot-coding-agent/customizing-the-development-environment-for-copilot-coding-agent does not mention Dev Containers / Codespaces at all. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
Github copilot coding agent (the one you assign to issues) does not use defined devcontainers / codespaces.
It makes sense as it's modeled as workflow enviroments and those don't use them either, but it's rather bad UX as one needs to duplicate setup (needed because within the workflow there's limited internet access) between CI+CD, copilot setup, and codespace / devcontainer.
It's especially jarring as copilot is marketed as another programmer / pair programmer and codespaces are exactle for that.
One potential solution would be to add a worflow action that'd simply run devcontainer setup inline for the copilot workflow enviromnet. And it'd be run automatically if config present.
Beta Was this translation helpful? Give feedback.
All reactions