| name | perplexity-ci-integration |
| description | Configure CI/CD for Perplexity Sonar API integrations with GitHub Actions.
Use when setting up automated testing, configuring CI pipelines,
or integrating Perplexity tests into your build process.
Trigger with phrases like "perplexity CI", "perplexity GitHub Actions",
"perplexity automated tests", "CI perplexity pipeline".
|
| allowed-tools | Read, Write, Edit, Bash(gh:*) |
| version | 1.12.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","perplexity","testing","ci-cd"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
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
set -euo pipefail
gh secret set PERPLEXITY_API_KEY --body "pplx-your-ci-key-here"
Step 2: GitHub Actions Workflow
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