Skip to content

feat(onboarding): add use cases selection step#2745

Merged
rmnbrd merged 5 commits into
stagingfrom
feat/onboarding-use-cases
Jun 10, 2026
Merged

feat(onboarding): add use cases selection step#2745
rmnbrd merged 5 commits into
stagingfrom
feat/onboarding-use-cases

Conversation

@jul-dan

@jul-dan jul-dan commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Issue: QOV-1998

Remove the question dropdown

Remove the hosting infra dropdown

Add a new step to ask for which use cases they are coming for (multi-select)

Send a posthog event with the usecases selection

Screenshots / Recordings

image

Testing

  • Changes tested locally in the relevant Console's pages and Storybooks
  • yarn test or yarn test -u (if you need to regenerate snapshots)
  • yarn format
  • yarn lint

PR Checklist

  • I followed naming, styling, and TypeScript rules (see .cursor/rules)
  • I performed a self-review (diff inspected, dead code removed)
  • I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
  • I only kept necessary comments, written in English (watch for useless AI comments)
  • I involved a designer to validate UI changes if I am not a designer
  • I covered new business logic with tests (unit)
  • I confirmed CI is green (Codecov red can be accepted)
  • I reviewed and executed locally any AI-assisted code

jul-dan and others added 3 commits June 9, 2026 11:35
Adds a dedicated step in the onboarding flow where users select what they
want to achieve with Qovery (multi-select cards). Removes infrastructure
hosting and qovery usage questions from the personalize step. Sends
PostHog events with user profile and selected use cases at each step.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… step

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@codecov

codecov Bot commented Jun 9, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 21.73913% with 18 lines in your changes missing coverage. Please review.
✅ Project coverage is 46.12%. Comparing base (582fa50) to head (f5d63b2).
⚠️ Report is 3 commits behind head on staging.

Files with missing lines Patch % Lines
.../feature/src/lib/step-use-cases/step-use-cases.tsx 0.00% 14 Missing ⚠️
.../src/lib/onboarding-project/onboarding-project.tsx 42.85% 4 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           staging    #2745      +/-   ##
===========================================
- Coverage    46.16%   46.12%   -0.05%     
===========================================
  Files         1208      757     -451     
  Lines        25695    19045    -6650     
  Branches      7572     5783    -1789     
===========================================
- Hits         11863     8784    -3079     
+ Misses       11761     8674    -3087     
+ Partials      2071     1587     -484     
Flag Coverage Δ
unittests 46.12% <21.73%> (-0.05%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Comment thread apps/console/src/routes/_authenticated/onboarding/personalize.tsx Outdated
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@jul-dan jul-dan force-pushed the feat/onboarding-use-cases branch from 582fc6f to f5d63b2 Compare June 9, 2026 15:05
@jul-dan jul-dan requested a review from RemiBonnet June 9, 2026 15:06
@rmnbrd rmnbrd merged commit f54df23 into staging Jun 10, 2026
12 checks passed
@rmnbrd rmnbrd deleted the feat/onboarding-use-cases branch June 10, 2026 08:23
@RemiBonnet

Copy link
Copy Markdown
Member

🎉 This PR is included in version 1.316.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants