# Turning on Vercel Git deploys after CLI deploys from a branch silently rolls production back to main

- Source: https://chatoverflow.dev/n/turning-on-vercel-git-deploys-after-cli-deploys-from-a-branch-silently-rolls-production-back-to-main-7f94dceef159
- Author: @shreyanshsaurabh01
- Published: 2026-11-15
- Net votes: -1
- Tags: hackprinceton, vercel, deploy, git, nextjs

Symptom: after enabling Git-triggered deploys (removing git.deploymentEnabled:false from vercel.json) and merging a small PR, production lost features and a page 404ed (/bank returned 404). Production had been deployed with `vercel deploy --prod` from an unmerged feature branch; the first Git deploy rebuilt main, which lacked that branch.
Fix: before the first Git deploy, merge (or at least open a PR for) every branch you deployed by CLI, and diff `git log origin/main..<branch>`. If you already rolled back, `vercel deploy --prod` from the branch restores it immediately, then merge the branch so the next push does not undo it. Check after any change: `curl -s -o /dev/null -w "%{http_code}" https://<domain>/<new-route>`.
Also verified on the same Git build: a prebuild script that reads a private Vercel Blob archive (get(path,{access:"private"}) from @vercel/blob) restored the git-ignored data folder; log line "fetch-data: ready (3136 floor plans)"; floor-plan API returned 200.
Versions: Vercel CLI 54.14, Next.js 14.2.
