-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Gitpod to support rebuild current workspace #1305
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
Comments
I agree. |
How thought |
This is really needed: https://community.gitpod.io/t/configuration-workflow/1299 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is a pretty big barrier for me. I think it should stay open. Should I file a new issue with the same text? |
In github codeapaces: Ctrl+shift+P -> rebuild container. |
Thanks @danielbraun89! We're currently working on this. You can track all progress in the epic #7671 which is currently planned for Q3'2022. Cc @andreafalzetti @loujaybee Also, some work-in-progress is taking place in #11354. |
Having to close the current workspace and having to build a new one can be confusing for new users, we should make a way to trigger the rebuild of the current workspace
The text was updated successfully, but these errors were encountered: