CI / CD Integration
Run PromptEval evaluations on every pull request to catch behavioral regressions before they reach production. Because PromptEval's judge is deterministic, the same output always produces the same score — evaluations are reproducible in CI.
Recommended CI workflow
Run evaluations before and after each change (use the version tag to label the commit).
Fail the build if a statistically significant regression is detected (p < 0.05, significant: true, direction: 'regression').
Gate on the lower bound of the CI, not the pass rate. If ci95[0] < your threshold, the confidence interval doesn't clear — require more runs or reject.
Store evaluation results as CI artifacts for audit and trend visibility.
GitHub Actions
The evaluation script
GitLab CI
Secret management
Store your PROMPTEVAL_API_KEY as a repository secret. Create a separate key per environment (dev/prod) so you can revoke CI access independently. Keys scoped to a project have no access to other projects.