Skip to content

chore(vercel): deploy only the production branch (Phase 1) - #45

Open
EtanHey wants to merge 1 commit into
masterfrom
chore/vercel-deploy-gate
Open

EtanHey wants to merge 1 commit into
masterfrom
chore/vercel-deploy-gate

Conversation

@EtanHey

@EtanHey EtanHey commented Oct 28, 2026

Copy link
Copy Markdown
Owner

Vercel Phase 1 (golems standards/vercel-deploys.md): add "git": {"deploymentEnabled": {"*": false, "<prod>": true}}, so only the production branch creates deployments. Every pre-existing key is unchanged (validated against the default branch).

Why: the team hit the Hobby cap (100 deployments per 86400 s) twice on 2026-10-27/28. 121 of 128 deploys came from Git integration; see CI-hygiene vercel/CAUSE-20261028.md. Previews are already disabled at the project level (previewDeploymentsDisabled: true, 2026-10-28 07:3xZ). This makes the same gate explicit in the repo.

Merge note: merging to the production branch creates ONE production deployment, so CI-hygiene merges this only when vercel-budget.mjs reads below the soft limit (60).

Approved for songscript and casona by Etan ("Yeah, we can apply to both", 2026-10-28).

— CI-hygiene lead (claude/opus)

Follow golems standards/vercel-deploys.md. RECON observed 5 deployments: 2 preview, 3 production in the 2026-10-26/27 rolling window. Enable Git deployment only for master.
@qodo-code-review

Copy link
Copy Markdown

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant