ci-pipeline

CI Pipeline

Platform: $0 (default: github-actions)

Type: $1 (default: full)

Steps

1. Analyze the project — Determine:

   • Build tool (npm, pnpm, turborepo)
   • Test framework (vitest, jest, playwright)
   • Lint tool (eslint, biome)
   • Deploy target (Vercel, Railway, Docker)
   • Monorepo? (turbo.json present)

2. Generate pipeline config:

GitHub Actions (full pipeline)

name: CI

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npm run lint

  test:
    runs-on: ubuntu-latest
    needs: lint
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npm test

  build:
    runs-on: ubuntu-latest
    needs: test
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npm run build

  deploy:
    runs-on: ubuntu-latest
    needs: build
    if: github.ref == 'refs/heads/main'
    steps:
      - uses: actions/checkout@v4
      # Deploy step depends on target platform

3. Add quality gates:

   • PR checks: lint + test must pass before merge
   • Branch protection: require status checks
   • Deploy only from main (or release branches)

4. Optimize:

   • Cache node_modules and build outputs
   • Use concurrency to cancel stale runs
   • Run lint and test in parallel when possible
   • Use turbo for monorepo builds

Output Format

Produce the CI config file(s):

• .github/workflows/ci.yml for GitHub Actions
• railway.json for Railway
• vercel.json for Vercel
• .gitlab-ci.yml for GitLab

Include comments explaining each section.

Constraints

• Never put secrets directly in CI config — use environment variables/secrets
• Pin action versions to specific commits or tags, not @main
• Keep pipeline under 10 minutes for PRs
• Only deploy from protected branches
• Include concurrency to prevent parallel deploys