Stop Vercel from building the main line - #122
Closed
ledwards wants to merge 1 commit into
Closed
Conversation
ledwards
added a commit
that referenced
this pull request
Aug 3, 2026
The Vercel project is connected at the repo level, so it attempted a build on every branch. Only ai-incarnations carries a vercel.json, so builds on this line had nothing to read and failed — posting a red check on this PR, which has nothing to do with Vercel. root.vc is served by Netlify. Set git.deploymentEnabled: false so branches carrying this file don't trigger a Vercel deployment. Byte-identical to the copy on #122, which lands the same file on main along with the README rationale. The two merge cleanly in either order. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Vercel project is connected at the repo level, so it attempted a build on every branch. Only ai-incarnations carries a vercel.json, so builds on this line had nothing to read and failed — posting a red check on PRs unrelated to Vercel, and on main itself. root.vc is served by Netlify. Set git.deploymentEnabled: false so branches carrying this file don't trigger a Vercel deployment. ai-incarnations has its own vercel.json without that key and keeps deploying successfully, so the parked experiment is unaffected. The README records why both files exist and how to resolve the conflict if that branch is ever merged down. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ledwards
force-pushed
the
vercel-disable-main-line
branch
from
August 3, 2026 23:47
f17fb81 to
fb22f10
Compare
ledwards
added a commit
that referenced
this pull request
Aug 4, 2026
Records that Netlify serves root.vc from dist/, that the Vercel project belongs to the parked ai-incarnations branch, and why the two vercel.json files deliberately differ — so nobody reconciles them and breaks that branch's deploys. Folded in from #122 so this line carries the whole change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Author
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
1 participant
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.
Two files, no behavior change to the site. Split out of #121 so it can land on its own — it's unrelated to the static-mirror work and fixes the red check on
mainand on every open PR.The problem
The Vercel project is connected at the repo level, so it attempted a build on every branch. Only
ai-incarnationscarries avercel.json; on this line Vercel had nothing to build, so every attempt failed and posted a redVercelcheck — onmainitself and on PRs that have nothing to do with Vercel.It wasn't a stale integration. It was a real failure of a deployment that was never supposed to happen here.
The fix
git.deploymentEnabled: false— documented as turning off automatic deployments for branches carrying the file.ai-incarnationsis unaffected. It carries its ownvercel.jsonwithout that key and its builds are green today. The README says so, and says not to reconcile the two files, because the difference is the point.Verified
Vercelcheck disappear there —testpasses, no red checkai-incarnationsstill reportsVercel: successmainhas no branch protection and no required status checks, so nothing depended on theVercelcontext existing. I checked before making a check vanish rather than turn greenserver: Netlifyandx-nf-request-idon the live response, apexAat75.2.60.5,www301s to apexNote for whoever merges
vercel.jsonhere is byte-identical to the copy on #121, so the two merge cleanly in either order. The README section lives only here to avoid a conflict.The remaining
Vercel Agent Reviewcheck reportsskipping — insufficient Credit. That's a billing state on the Vercel account, unrelated, and it reports neutral rather than failing.🤖 Generated with Claude Code