Skip to content

Create new workspace from stopped workspace page + show if configuration has changed. #16232

@loujaybee

Description

@loujaybee

Context: When updating your gitpod configuration, it's not obvious that configuration updates do not apply to a restarted workspace, but instead a new workspace must be started for the configuration change to apply.

Suggestion(s):

  1. Show on the stopped workspace page that the configuration is "dirty" - Provide some warning to users that they have updated their configuration, but these changes will not be applied to the restarted workspace, similar to how we show "files changed" in the dashboard when a user updates files but does not commit. Also:
  2. Option to start a "new workspace" - The stop workspace page could have another call to action for the user to create a new workspace based on the same context URL of the stopped workspace.

Aside: "Open" workspace seems ambiguous in the intent of the button, should we consider altering this to "restart" workspace? Or is there a specific reason for it to be named "open"?

Stopped workspace page
image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions