feat(frontend): Discord and GitHub usernames in org onboarding - #2832
Conversation
Collect optional support identity during organization creation so Capgo can recognize cloud customers faster when they need help. Co-authored-by: Cursor <cursoragent@cursor.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_c4f4417e-38ce-4c28-b343-c8960a16cd90) |
📝 WalkthroughWalkthroughThe onboarding flow collects optional Discord and GitHub support identities. GitHub profiles can be looked up, confirmed, or removed. Organization onboarding saves the Discord username before organization creation and adds localized guidance. ChangesSupport identity onboarding
Estimated code review effort: 3 (Moderate) | ~30 minutes Sequence Diagram(s)sequenceDiagram
participant User
participant OnboardingSupportUsernames
participant GitHubProfileLookup
participant Supabase
User->>OnboardingSupportUsernames: Enter GitHub username
OnboardingSupportUsernames->>GitHubProfileLookup: Look up profile
GitHubProfileLookup-->>OnboardingSupportUsernames: Return profile or error
User->>OnboardingSupportUsernames: Confirm or remove account
OnboardingSupportUsernames->>Supabase: Persist GitHub account change
Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
Spell out that Discord/GitHub usernames are used to match Capgo Cloud accounts when customers open support issues. Co-authored-by: Cursor <cursoragent@cursor.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_6e85078a-597e-438a-8dd5-3fdd2bc7605f) |
Merging this PR will not alter performance
Comparing 
Footnotes
|
Make GitHub username help copy state that priority support is included from Maker and above, and for all accounts during trial. Co-authored-by: Cursor <cursoragent@cursor.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_3d84480a-bc9d-44da-84a0-f4c414171e4e) |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/dashboard/OnboardingSupportUsernames.vue`:
- Around line 57-84: Update findGitHubProfile to trim githubUsernameInput.value
before passing it to getGitHubProfile, and return early when the trimmed
username is empty. This guard must also cover the `@keydown.enter.prevent`
shortcut so pressing Enter with only whitespace does not trigger a lookup, while
preserving the existing loading and lookup-generation behavior.
- Around line 44-153: Extract the duplicated lookup, confirmation, removal, and
users-table update logic from openGitHubProfileDialog, findGitHubProfile,
confirmGitHubProfile, and clearGitHubProfile into a shared GitHub profile
composable. Update both consuming components to use that composable while
preserving their existing loading, generation guards, error handling, user-state
updates, dialog, and toast behavior.
In `@src/pages/onboarding/organization.vue`:
- Around line 392-416: Update saveSupportUsernames to surface persistence
failures to its caller instead of only logging and returning. Propagate the
Supabase update error or throw when error or user is missing, and ensure the
onboarding flow that invokes saveSupportUsernames before organization creation
handles the failure by stopping creation and presenting a visible error to the
user.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 0a4bb73a-b942-4189-b185-62a5fc07db26
📒 Files selected for processing (3)
messages/en.jsonsrc/components/dashboard/OnboardingSupportUsernames.vuesrc/pages/onboarding/organization.vue
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
Cap-go/capacitor-updater(manual)
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Redesign Discord/GitHub support fields with clearer hierarchy, benefit chips for Maker+ and trial priority, and a real local console screenshot for the PR. Co-authored-by: Cursor <cursoragent@cursor.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_5c91abb6-aa94-45ac-afb0-9ebeeda3923c) |
Keep only the OnboardingSupportUsernames component registration. Co-authored-by: Cursor <cursoragent@cursor.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_7b14b210-a86f-46cf-9824-0626371512f4) |
Extract shared GitHub verify dialog, clarify new-user org onboarding placement, surface Discord save failures, and prompt logged-in users weekly with a discreet forever-dismiss link. Co-authored-by: Cursor <cursoragent@cursor.com>
Follow-up (AI generated)Addressed review comments:
Also added:
|
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_485b7bbe-ed5a-4ebc-94c0-42e188f8153b) |
|
1 participant
Summary (AI generated)
Onboarding · Create organizationon the new-user path so placement is explicitMotivation (AI generated)
Support identity fields were easy to miss after onboarding. Collecting them in the org-creation onboarding step, then gently reminding weekly, increases match rate for Capgo Cloud support on Discord/GitHub.
Business Impact (AI generated)
Faster Capgo Cloud support triage. Maker+ / trial priority support messaging is visible in onboarding and the weekly prompt.
Where this sits in onboarding (AI generated)
New-user Capgo onboarding flow:
/onboarding/app— app details / intent/onboarding/organization— create organization ← Discord + GitHub block is hereAdditional-org create (
?source=org-switcher) shows the same block without the new-user onboarding eyebrow.Visual changes (AI generated)
Local console screenshot:
Test Plan (AI generated)
Onboarding · Create organization+ support fields/onboarding/*Generated with AI
Note
Low Risk
User-profile field updates and client-side prompt gating only; no auth or billing changes, with org create guarded on Discord save failure.
Overview
Optional Discord and verified GitHub are collected on the create organization onboarding step; Discord is persisted before org creation (failure shows a toast and blocks org create). Copy explains how usernames tie Capgo Cloud accounts to Discord/GitHub support, including Maker+ / trial priority messaging.
Shared UI includes
OnboardingSupportUsernames,GitHubProfileDialog, anduseGitHubProfileDialog(account settings drops inline GitHub dialog logic in favor of these). App-wideSupportUsernamesPromptappears after ~2.5s when the user is missing both usernames, with remind-later (weekly vialocalStorage) and don't-ask-again; it is suppressed on auth/onboarding routes and when another dialog is open.English i18n strings are expanded for help text, onboarding benefits, and the prompt.
Reviewed by Cursor Bugbot for commit 3a7951b. Bugbot is set up for automated code reviews on this repo. Configure here.