Skip to content
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

Menu item in VSCode to stop workspace and start a new one aka rebuild workspace #9956

Closed
ghuntley opened this issue May 12, 2022 · 1 comment
Labels
meta: never-stale This issue can never become stale

Comments

@ghuntley
Copy link
Contributor

ghuntley commented May 12, 2022

Is your feature request related to a problem? Please describe

Describe the behaviour you'd like

Screen Shot 2022-05-12 at 4 08 42 pm

From: https://twitter.com/hrittikhere/status/1524630369575702528?s=20&t=jmOoNX6wzNVo0bJV93clDQ

Additional

@hrittikhere
Copy link

So, to understand this issue, we need to understand where I am coming from first. I am using codespace since Day 2 and got introduced to GitPod much later. I like gitpod for the .gitpod yaml and the containers are a bit more robust if compared to codespaces.

One of the good features of codespaces is allowing for rebuilding containers with a click:

image

Now, we can do that in GitPod, but then I think keeping two containers will be a waste of resources at the scale you operate and I also like to keep my portal clean. I am lazy enough to go delete the containers. I will be waiting for 90 days for auto delete for unpinned containers to kick in.

Some folks might need two containers but for most, rebuilding one when things go haywire is the best shot.

Haywire? A few instances for me when I needed to rebuild a container were:

  1. Messing with network configuration and mess things up. Now I can correct things or build a new one easily.
  2. Dependency issues where I install a lot of packages to test my code and new stuff but I can send all of them to requirements. Now I can remove all of them manually or can build a new one and move forward with the one I need.
  3. Sometimes things break. I am not sure how but there's some issue with installation or configuration. Creating one without leaving the tab is fast and effortless.

image

I can't think of anything more now. Options like recreating a container without leaving the tab will be helpful.

What do you think?

@ghuntley ghuntley added the meta: never-stale This issue can never become stale label May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale
Projects
None yet
Development

No branches or pull requests

2 participants