ci: deploy to Vercel from GitHub Actions - #670
Merged
Merged
Conversation
- Add production deploy job on pushes to main - Add preview deploys for same-repo PR branches - Ignore .vercel and .env* locally Uses a VERCEL_TOKEN repo secret instead of the Vercel GitHub App, so no app install is needed on the inkonchain org.
Pin actions/checkout to a hash, set persist-credentials: false, and scope permissions to contents: read on both new jobs.
devknight-ink
force-pushed
the
chore/vercel-deploy-ci
branch
from
September 14, 2026 14:33
7035aad to
fc4f4a9
Compare
pull Bot
pushed a commit
to sigma7863/inkonchain-docs
that referenced
this pull request
Sep 14, 2026
Docs now deploy to Vercel via CI (inkonchain#670) and docs.inkonchain.com has cut over. Remove the unused Dockerfile, .dockerignore, amplify.yml and the docker-publish job, and serialize production deploys with a concurrency group.
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
2 participants
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
Adds Vercel deployment to the existing CI workflow:
mainWhy
We're moving docs hosting off Kraken infra onto the foundation-owned Vercel team. The repo lives in the
inkonchainorg where the Vercel GitHub App isn't installed, so this deploys via CLI with aVERCEL_TOKENrepo secret instead. No org-level app install needed.Before merging
A
VERCEL_TOKENsecret (scoped to the Ink Foundation Vercel team) must be added to this repo's Actions secrets.Notes
docker-publishjob stays untouched until DNS cutover; Kraken's deployment keeps working in the meantime.Dockerfile,amplify.yml, and thedocker-publishjob.Heads up for the future
If the Vercel GitHub App is ever installed on the
inkonchainorg and the repo gets connected natively (the "Connect Git Repository" button in the Vercel dashboard), remove thevercel-previewandvercel-deployjobs in the same change, otherwise every merge deploys twice.