Files
lets-event/.github/workflows/deploy.yml
T
rmcamposandClaude Sonnet 4.6 1bb2feb770
Deploy to Vercel / Deploy to Vercel (push) Successful in 2m43s
ci: use project ID secrets instead of vercel pull for Gitea compatibility
vercel pull --yes fails on Gitea repos (only supports GitHub/GitLab/Bitbucket).
Build project.json from VERCEL_PROJECT_ID and VERCEL_ORG_ID secrets instead.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-18 20:54:19 -03:00

34 lines
824 B
YAML

name: Deploy to Vercel
on:
push:
branches: [main]
jobs:
deploy:
name: Deploy to Vercel
runs-on: easynode-debian
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Cache npm dependencies
uses: actions/cache@v3
with:
path: ~/.npm
key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-npm-
- name: Install Vercel CLI
run: npm install -g vercel
- name: Link Vercel Project
run: |
mkdir -p .vercel
echo '{"projectId":"${{ secrets.VERCEL_PROJECT_ID }}","orgId":"${{ secrets.VERCEL_ORG_ID }}"}' > .vercel/project.json
- name: Deploy to Vercel
run: vercel deploy --prod --token=${{ secrets.VERCEL_TOKEN }} --yes