Prep for new onboarding flow #16469
Merged
Prep for new onboarding flow #16469
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
started the job as gitpod-build-bmh-new-signup-flow-flagged.1 because the annotations in the pull request description changed |
selfcontained
changed the title
|
/hold for feedback |
|
/werft run 👍 started the job as gitpod-build-bmh-new-signup-flow-flagged.2 |
geropl
approved these changes
Feb 21, 2023
selfcontained
force-pushed
the
bmh/new-signup-flow-flagged
branch
from
25f89de to
d73eb89
Compare
|
/unhold |
roboquat
added
deployed: webapp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Stubbing out a placeholder for the new onboarding flow. It's gated behind the
newSignupFlowfeature flag, which is off everywhere atm. When this is enabled, we'll also suppress existing onboarding flows, like IDE Selection, and Profile info nudging.How to test
This PR shouldn't change any of the user experience.
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-testPublish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/previewIf enabled this will create the environment on GCE infra
Valid options are
all,workspace,webapp,ide,jetbrains,vscode,ssh