Fix admin dashboard status vocabulary and GitHub enrichment mismatches - #32
Merged
Merged
Conversation
The dashboard showed all 6 projects as "Killed" with 0 active and $0 MRR despite 3 apps being genuinely live. Root cause: registry.json uses a "live"/"coming_soon" status vocabulary, but RegistryProject's type and StatusBadge only understood "active"/"killed" — anything else silently rendered as "Killed" and was excluded from the active count. Extended the vocabulary to a real 3-state model (active/coming_soon/ killed, matching what the Python provisioning script actually writes for newly created projects) instead of forcing coming-soon apps into a binary active/killed choice. Added a "Coming Soon" badge variant. Also fixed the Active Projects stat card, which hardcoded everyone not active as "killed" regardless of their real status. Separately, GitHub star/fork enrichment showed "—" for every project. Root cause was a typo'd org name that no longer exists on GitHub (crewcricle vs crewcircle — this is a local env var fix, not reflected in this diff). While tracing it, also found one registry ID that doesn't match its real GitHub repo name (taxflowai vs taxflow-ai, a hyphen difference GitHub's case-insensitive matching can't paper over). Added a small override map in github.ts rather than renaming the registry ID, which is used as a key across routes/costs/provisioning. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
The admin dashboard showed all 6 projects as "Killed" (0 active, $0 MRR) despite 3 apps being genuinely live, and every GitHub column showed "—" with no star/fork data.
Status vocabulary mismatch:
registry.jsonuses"live"/"coming_soon", butRegistryProject's type andStatusBadgeonly understood"active"/"killed"— anything else silently rendered "Killed" and was excluded from the active count. Extended to a real 3-state model (active/coming_soon/killed, matching what the Python provisioning script actually writes for new projects) with a new amber "Coming Soon" badge, and fixed the stat-card subtitle that hardcoded everyone-not-active as "killed".GitHub enrichment: root cause was
CC_GITHUB_USERNAME=crewcricle(typo, org no longer exists) in local env — not part of this diff since it's a local-only fix. While tracing it, also foundtaxflowai(registry ID) doesn't match the real GitHub repotaxflow-ai(hyphen). Added a smallREPO_NAME_OVERRIDESmap ingithub.tsrather than renaming the registry ID, which is used as a key across routes/costs/provisioning.Test plan
npx tsc --noEmit— cleannpx eslint src --quiet— clean🤖 Generated with Claude Code