I’m on a Hobby plan, so I cannot create a dedicated CI/CD / Environments support case. I’m posting here to ask whether this behavior is expected or caused by hidden project state.
Issue: A non-production Git branch is being classified as a Production Deployment even though the project Production Branch is set to main.
Team: fandom-harbor
Project: fandom-harbor-admin
Repository: reallllmann-oss/FandomHarbor
Root Directory: apps/admin
Production Branch: main
Preview Branch Tracking: All unassigned git branches
Branch incorrectly classified as Production: codex/admin-preview-baseline
Commit SHA: 903bf70a6dc370090362098d26bedd6bf68af529
Expected behavior: codex/admin-preview-baseline is not the Production Branch, so it should create a Preview Deployment.
Actual behavior: The deployment from codex/admin-preview-baseline was classified as production / Production.
Current state: Preview deployments: 0 Production deployments: 0 The incorrectly classified deployments were cancelled and deleted. The project currently has no active deployment.
Dashboard checks:
- Project Name: fandom-harbor-admin
- Domain: fandom-harbor-admin.vercel.app
- Domain Status: No Deployment
- Git Repository: reallllmann-oss/FandomHarbor
- Production Branch: main
- Preview Branch Tracking: All unassigned git branches
- Framework Preset: Next.js
- Root Directory: apps/admin
- Build Command: turbo run build, auto-detected, Override off
- Install Command: pnpm install
- Output Directory: Next.js default
- Deploy Hooks: none
- Custom Environments: none
- Ignored Build Step: Automatic
- No GitHub Actions deployment workflow
- No vercel.json
- No vercel.ts
Question: Why would a non-production Git branch be classified as a Production Deployment? Is there a hidden project-level rule, first-deployment initialization behavior, or internal project state that could cause this? How can I safely generate a Preview Deployment for this project before any Production Deployment exists?
