-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[projects] remove configuration page from wizard #7102
Conversation
f8cb1cb
to
ea98254
Compare
/werft help 👍 You can interact with werft using:
|
comments on the current implementation
|
ea98254
to
3312ee5
Compare
I had to redeploy the whole thing. Workspaces failed to start after a rebase, unfortunately. |
/werft run 👍 started the job as gitpod-build-at-config-page.8 |
bce4aa2
to
33734f0
Compare
33734f0
to
82d3603
Compare
@jldec, it's updated, and build is triggered. Please note, workspaces do fail to start on preview environments at the moment. That's nothing to be part of this PR. |
82d3603
to
49b28c4
Compare
setSourceOfConfig("db"); | ||
setGuessedConfigString(await guessedConfigStringPromise || `tasks: | ||
- init: | | ||
echo 'TODO: build project' | ||
command: | | ||
echo 'TODO: start app'`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there can be a race here -- if await guessedConfigStringPromise
takes too long, you might call server.setProjectConfiguration(project.id, undefined)
on line 154.
Safer the other way around:
setSourceOfConfig("db"); | |
setGuessedConfigString(await guessedConfigStringPromise || `tasks: | |
- init: | | |
echo 'TODO: build project' | |
command: | | |
echo 'TODO: start app'`); | |
setGuessedConfigString(await guessedConfigStringPromise || `tasks: | |
- init: | | |
echo 'TODO: build project' | |
command: | | |
echo 'TODO: start app'`); | |
setSourceOfConfig("db"); |
<p className="mt-2 text-gray-500 text-center text-base">Created <a className="gp-link" href={projectLink}>{project.name}</a> | ||
<br /> {location} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: This deviates slightly from the spec, but I'd find it a lot better to explicitly state what's a "project" and what's a "team", just to avoid any possible confusion here (as we've seen in user testing, users are sometimes confused between workspace vs team vs project, so might as well be 100% clear here).
Also, the new line between the two doesn't make sense, and actually looks like a UI bug:
<p className="mt-2 text-gray-500 text-center text-base">Created <a className="gp-link" href={projectLink}>{project.name}</a> | |
<br /> {location} | |
<p className="mt-2 text-gray-500 text-center text-base">Created project <a className="gp-link" href={projectLink}>{project.name}</a> {location} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which spec do you mean? cf. https://gitpod.slack.com/archives/C02EN94AEPL/p1638903077402500?thread_ts=1638877444.381700&cid=C02EN94AEPL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me, spec = visuals added to an issue that show what we want to have.
Here, it's #7098 (see "refined visual" at the bottom of the issue description)
However, I slightly disagree with the spec, because I think:
Project Created
Created project [test-project-2] in team [team-1]
is clearer than:
Project created
Created [test-project-2]
in [team-1]
Codecov Report
@@ Coverage Diff @@
## main #7102 +/- ##
===========================================
+ Coverage 19.04% 31.47% +12.42%
===========================================
Files 2 28 +26
Lines 168 4823 +4655
===========================================
+ Hits 32 1518 +1486
- Misses 134 3187 +3053
- Partials 2 118 +116
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
49b28c4
to
0cae03d
Compare
instead of showing the configuration page, let's show a simple `New Workspace` button to start a workspace. we rescue the auto-inferred configuration or use the existing one to trigger a prebuild right away. Co-authored-by: Jan Keromnes <[email protected]> Co-authored-by: Alex Tugarev <[email protected]>
0cae03d
to
9030481
Compare
put some comments in #7098 (comment) /lgtm |
LGTM label has been added. Git tree hash: a17be6f3e98c535a7f152f53898151565c09af6c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jldec Associated issue: #7098 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
instead of showing the configuration page, let's show a simple
New Workspace
button to start a workspace.we rescue the auto-inferred configuration or use the existing one to trigger a prebuild right away.
many thanks to @jankeromnes to help get this done! 💯
Resolves #7098 and #7088