fix(webapp): onboard new cloud orgs via plan selection; allow Free plan without GitHub verification#4109
Merged
Merged
Conversation
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
💤 Files with no reviewable changes (3)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
📜 Recent review details⏰ Context from checks skipped due to timeout. (24)
|
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The PR description explains the changes and testing, but it omits the required issue link, checklist, changelog, and screenshots sections. | Add the template sections: Closes #issue, checklist items, a short changelog, and screenshots, or mark N/A where not applicable. |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title matches the main change: onboarding new cloud orgs through plan selection and removing the GitHub verification requirement for Free. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
📝 Generate docstrings
- Create stacked PR
- Commit on current branch
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Commit unit tests in branch
fix/free-plan-onboarding
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…tion New managed-cloud orgs were created already activated, so they skipped the select-plan flow that provisions their billing entitlement — leaving the free-tier usage cap unenforced. Create managed-cloud orgs deactivated so they're routed through select-plan, which activates them once a plan is selected. Self-hosters have no billing gate and remain active immediately. Rename the Organization.v3Enabled Prisma field to isActivated (mapped to the existing v3Enabled column, so the database and billing service are unchanged) to better reflect what the flag now gates.
matt-aitken
force-pushed
the
fix/free-plan-onboarding
branch
from
d8bc6fa to
7fa8c43
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
matt-aitken
force-pushed
the
fix/free-plan-onboarding
branch
from
7fa8c43 to
090c64a
Compare
Selecting Free now provisions the plan immediately instead of routing through a GitHub connect/verification step. Remove the 'Unlock Free plan' / 'Connect to GitHub' dialog, the GitHub-verified badge, and the account- rejected state from the plan picker, simplify the setPlan free-result handling to a success redirect, and delete the now-unreachable free-connect return routes. The billing service provisions the free plan directly.
matt-aitken
force-pushed
the
fix/free-plan-onboarding
branch
from
090c64a to
3cfc891
Compare
myftija
approved these changes
Jul 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What & why
Two related fixes to how new cloud organizations get onboarded onto the Free plan.
1. Route new cloud orgs through plan selection
New cloud organizations were created already activated, so they skipped the plan-selection step and went straight to creating projects — which meant their plan and usage limits were never set up. They're now created deactivated and routed through plan selection, which activates them once a plan is chosen. Self-hosted installs have no plan-selection step, so they're activated immediately on creation and are unaffected.
The
Organization.v3Enabledfield is renamed toisActivatedto better describe what it now gates. It's mapped to the existingv3Enabledcolumn, so there's no data migration — only a schema/code rename.2. Allow selecting the Free plan without GitHub verification
Choosing the Free plan no longer requires connecting and verifying a GitHub account. The plan is applied immediately when selected. This removes:
Notes
Testing
Verified locally end to end: a new cloud org is routed to plan selection, the Free plan applies in one click with no GitHub step, the org is activated, its usage allowance is provisioned, and it lands on the new-project page.
🤖 Generated with Claude Code