Add setting for default profile for new codespace connections #184569
Replies: 1 comment
-
|
💬 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.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
Problem
On a new Codespace connection in vscode, Codespaces always uses my default profile. My default profile is heavyweight with extensions and causes the codespace to take forever to start up as extensions are copied and installed. As a workaround I made my default profile very sparse with extensions, and have a secondary profile where my "usual" extensions live. This is very awkward DX.
Solution
I would like an option in the vscode extension options something like
github.codespaces.defaultProfile, which will let me specify which profile to use when connecting to a new codespace by default. If I had this I can make a separate slim "codespaces" profile that inherits from my default profile settings, but only includes the minimum extensions to start quickly, and from there I can select other profiles for C#, etc.Beta Was this translation helpful? Give feedback.
All reactions