Repository navigation
ci: let Vercel build docs.doublezero.xyz from main - #224
Merged
Merged
Conversation
Vercel builds the site itself through its GitHub app. vercel.json runs scripts/vercel-build.sh, which is the docs workflow's build: the same hash-pinned packages for Python 3.12, the same allowed warning, and the same site tar into build-vercel-output.sh. Branches are skipped, so only main builds there. No Vercel token is stored in this repository.
martinsander00
approved these changes
Oct 28, 2026
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.
Summary
mainthrough its GitHub app, so a merge publishes both sites without a manual deploy.vercel.jsonruns the newscripts/vercel-build.sh. It is the docs workflow's build: the same hash-pinned packages for Python 3.12, the same one allowed warning, and the same site tar intobuild-vercel-output.sh.vercel deployfrom the CLI, still runs.Deploy / rollout
doublezero-docsproject tomalbeclabs/docswithmainas the production branch, and keep fork protection on.mainand check docs.doublezero.xyz.Testing
vercel deployfrom this branch built on Vercel's build machines with Python 3.12, installed every pinned package, and showed only the allowed warning.redirects.jsonanswered 308 to the same target as production, and/.well-known/mcp/server-card.json,/hyperliquid/peering/and/ja/hyperliquid/peering/answered 200, as production does.