-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epic: VS Code Desktop GA #7184
Comments
Moving to Q3, work will continue towards VS Code and GA, such as: #8513 but this work is unlikely to conclude in Q2. |
Moving to Q4 on roadmap, however most of the critical issues are now addressed, we mostly just need to update docs and announce! ... Watch this space ! |
Some issues reported, need to resolve and link them here before we close. |
Yeah, like this one #14626, don't know the proper section it should be. @loujaybee 🙏 |
Final task is to finish documentation: |
The beta label in documentation has now been lifted 🙏 |
- User can establish a stable SSH connection for VS Code Desktop
Required for GA
Core experience
Issues related to the "core" of the Gitpod experience: ports, extensions,
gitpod.yml
integrations. Should be no significant parity to VS Code Browser: all ports forwarded, ports behaviours accessible, e.g. ports public, etc.Connections (filter:
aspect: connections
)Users need a stable connection to Gitpod, that doesn't interfere with other remote development use cases. Where disconnects occur, these should be transparent, and recoverable so users can easily re-connect.
Supporting documentation (filter:
team:ide
)All important aspects of configuring and setting up VS Code Desktop integration should be covered in documentation.
Not required for GA
Completed
gitpod_ssh_config-*
file #8337The text was updated successfully, but these errors were encountered: