perplexity-ci-integration

# Perplexity CI Integration ## Overview Set up CI/CD pipelines for Perplexity Sonar API integrations. Key CI concerns: live API calls cost money (use mocks for unit tests, reserve live calls for integration tests), API keys must be in GitHub Secrets, and rate limits apply even in CI. ## Prerequisites - GitHub repository with Actions enabled - Perplexity API key for CI (separate from production) - Test suite with mocked and live test separation ## Instructions ### Step 1: Configure GitHub Secret ```bash set -euo pipefail # Store API key as a GitHub secret gh secret set PERPLEXITY_API_KEY --body "pplx-your-ci-key-here" ``` ### Step 2: GitHub Actions Workflow ```yaml # .github/workflows/perplexity-tests.yml name: Perplexity Integration Tests on: push: branches: [main] pull_request: branches: [main] jobs: unit-tests: 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 test -- --coverage # Unit tests use mocked responses — no API key needed integration-tests: runs-on: ubuntu-latest needs: unit-tests if: github.event_name == 'push' && github.ref == 'refs/heads/main' env: PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: "20" cache: "npm" ...