GitHub Actions
The most common way teams run Omic in CI. One step in your workflow runs the suite, compares it against main, and blocks the merge when a case regresses.
The workflow step
Add this to your workflow file:
•
omic/setup-action — installs the CLI and restores the cache
•
omic run --ci — runs the suite against the pull request branch
•
--baseline origin/main — compares against the target branch
Secrets and keys
Provider keys come from your repository secrets:
•
OPENAI_API_KEY — read from the environment, never from the suite
•
OMIC_TOKEN — optional — only needed to push runs to Cloud
•
Fork-safe — runs from forks skip judged scorers by default.
Reporting on the PR
Results land where the review already happens:
•
Inline comment — the failing cases and their diffs, on the pull request.
•
Status check — a required check you can gate branch protection on.
•
Run link — opens the full run in Cloud, if you have it connected.