-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Enable "New Workspace" button in Project Configuration without first having to use "Run Prebuild" button #6303
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
Comments
Also for the Prebuild option, I think we should remove the logs view on the right and instead open a new window with a workspace starting in prebuild. |
Cross-posting relevant issue based on #6303 (comment) above: |
/schedule |
@jldec: Issue scheduled in the meta team (WIP: 0) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I believe new users just entering gitpod and ending up here will be a little uncertain what to do next, when there are two buttons. I think having one button that starts a workspace with a prebuild in a new tab would be simpler and better. Worth noting that the singular rebuild page is a great place to educate people about what a rebuild is. Also, it offers a button to skip this, for people who are a little impatient. |
I started working on this in PR #6389. It's just a draft of a single action that would combine:
|
/assign @AlexTugarev |
Discussed with @gtsiolis and @AlexTugarev. More details in PR #6389 |
@JanKoehnlein I expected this to move to "groundwork: awaiting deployment" when it was auto-merged after I approved #6389. |
When I create a new Project, I may not wish to configure a Prebuild before opening a Workspace.
The
New Workspace
button is currently disabled, until a Prebuild is run. Let's enable it always.The text was updated successfully, but these errors were encountered: