gitpod-io / gitpod-io/gitpod

Surface context on the workspace start page when creating a new or opening an existing workspace

Open
#13,712 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component: dashboard feature: workspace start page meta: never-stale team: webapp type: improvement
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

Problem to solve

Currently, when users create a new workspace or open an existing workspace, they go through the workspace start page (Checking, Creating, etc) without surfacing the original context.

Sometimes, opening a workspace can take up to 5 minutes and users can be lost as we're showing a generic page for any context or repository they open.

Proposal

There are several improvements we could make on the workspace start page (see relevant discussion (internal)), but a good MVC (minimal viable change) here could be to simply reuse the context element as we do with the rest of the workspace start phases (STOPPED, TIMED-OUT, etc.).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the workspace start page and its context element, then trace the create and open phases described in the issue. Done means the original workspace or repository context is visible during Checking and Creating, matching the existing context shown in the STOPPED and TIMED-OUT phases.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.