Repository navigation
Stop Vercel from building the spec-drift-status branch - #13
Merged
Merged
Conversation
Vercel reads vercel.json from the commit it deploys, so the
deploymentEnabled setting on main never reached the status branch, which
holds only spec-drift.json. Every status commit started a preview build that
failed ("npm run vercel-build" exited with 1). The watch now writes a
vercel.json that turns deployments off into the status branch with each
publish, and main's vercel.json, whose only setting had no effect, is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VeACDNmxsBifFG4eSqRsUi
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
What this PR does
Every weekly status commit to the
spec-drift-statusbranch started a Vercel preview build that failed ("npm run vercel-build" exited with 1) and emailed a failure. The setting meant to prevent this sat inmain'svercel.json, but Vercel readsvercel.jsonfrom the commit it deploys, and the status branch holds onlyspec-drift.json. Now the watch writes avercel.jsonthat turns deployments off into the status branch each time it publishes, so status commits no longer start a build. The site, which readsspec-drift.jsonfrom that branch, is unaffected.Changes
.github/workflows/spec-drift-watch.ymlwrites{ "git": { "deploymentEnabled": false } }asvercel.jsonnext tospec-drift.jsonand commits both. On the first run after merge, the file is new, so the step commits even when the status itself is unchanged. That commit already carries the file, so it doesn't deploy either.main'svercel.jsonremoved: its only setting was thisdeploymentEnabledentry for the status branch, which had no effect, so leaving it in would mislead the next reader.Checks
vercel.jsonand with an unchanged status. Both pushed a commit holdingspec-drift.jsonand a validvercel.json.bash -non the stepGenerated by Claude Code