Skip to content

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

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

Open
gtsiolis opened this issue Oct 10, 2022 · 3 comments
Labels
component: dashboard feature: workspace start page meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code

Comments

@gtsiolis
Copy link
Contributor

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.).

@gtsiolis gtsiolis added good-first-issue component: dashboard type: improvement Improves an existing feature or existing code team: webapp Issue belongs to the WebApp team feature: workspace start page labels Oct 10, 2022
@Hardik500
Copy link
Contributor

@gtsiolis I would like to work on this issue. Is this up for grab, or some discussion is required on this one?

@gtsiolis
Copy link
Contributor Author

gtsiolis commented Nov 7, 2022

@Hardik500 Yes, using the context element should be ok to add here. Let us know if you open a PR for resolving this.

@stale
Copy link

stale bot commented Feb 19, 2023

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Feb 19, 2023
@gtsiolis gtsiolis added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard feature: workspace start page meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code
Projects
None yet
Development

No branches or pull requests

2 participants