Configure Vercel CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Vercel tests into your build process. Trigger with phrases like "vercel CI", "vercel GitHub Actions", "vercel automated tests", "CI vercel".
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install vercel-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Set up CI/CD pipelines for Vercel integrations with automated testing.
Create .github/workflows/vercel-integration.yml:
name: Vercel Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
VERCEL_API_KEY: ${{ secrets.VERCEL_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
VERCEL_API_KEY: ${{ secrets.VERCEL_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
gh secret set VERCEL_API_KEY --body "sk_test_***"
describe('Vercel Integration', () => {
it.skipIf(!process.env.VERCEL_API_KEY)('should connect', async () => {
const client = getVercelClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
VERCEL_API_KEY: ${{ secrets.VERCEL_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Vercel production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
required_status_checks:
- "test"
- "vercel-integration"
For deployment patterns, see vercel-deploy-integration.