che icon indicating copy to clipboard operation
che copied to clipboard
verified publisher icon eclipse-che

Improve the workflow for creating a new workspace from scratch

Open cgruver opened this issue 7 months ago • 3 comments

Is your enhancement related to a problem? Please describe

There currently is not an intuitive workflow for bootstrapping a new workspace.

  1. Create an empty workspace
  2. Clone or create your target code repository
  3. Create a devfile
  4. Test the devfile by restarting from local devfile
  5. Commit the changes to the git repository
  6. Delete the initial empty workspace
  7. Create a new workspace from the git repository

This workflow is very cumbersome and requires a fair amount of forethought.

Describe the solution you'd like

An initial iteration for simplifying the workflow -

  1. Allow users to give a new workspace a name from the dashboard, potentially overriding the name in a devfile.
  2. Add an action to the Welcome tab to generate a new devfile. For example, when using the empty workspace or when the git repo does not include a devfile.
  • The generated devfile should be generated in a folder of the users choosing.
  • The generated devfile should reflect the configuration of the default devfile as defined in the CheCluster CR.
  • The generated devfile should use the name given to the workspace.

Describe alternatives you've considered

No response

Additional context

No response

cgruver avatar May 16 '25 11:05 cgruver

Hi @cgruver , you can simplify the bootstrapping of a new workspace a bit if you have a target code repository: instead of creating an empty workspace, use the Import from Git form:

Image

This will create a new workspace and clone the source code from the repository.

cc @ibuziuk

akurinnoy avatar May 16 '25 13:05 akurinnoy

@akurinnoy understood.

I still believe that it would be nice to be able to declare a workspace name rather than have one auto-generated.

I've observed a lot of users struggle to get started with a devfile. Being about to click a button to generate one from the default devfile would be a good start.

cgruver avatar May 16 '25 14:05 cgruver

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

che-bot avatar Nov 13 '25 08:11 che-bot