DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to gate promptfoo eval results before a release with Eval Forge

Convert promptfoo JSON output into a portable artifact and run a policy gate on it.

Who it is forA developer who already runs promptfoo evaluations and wants a release decision in CI without sending prompts or traces anywhere.

The problempromptfoo output uses its own result shape, so it cannot be compared with a baseline or fed to a CI policy directly.

The outcomeA portable Eval Forge artifact built from promptfoo results, checked by a policy file that does not copy prompts, responses, or traces.

What you need first

  • Python 3 with pip and a virtual environment
  • A committed evaluation artifact, or results from promptfoo, Ragas, or DeepEval
  • Git, and a GitHub repository if you want the composite Action
  • Docker, only if you use the Compose path

Steps

  1. Install the gate with pip install evalforge-ci.
  2. Run promptfoo eval --output build/promptfoo-results.json.
  3. Run evalforge import promptfoo build/promptfoo-results.json --output build/evalforge-artifact.json --source-revision "$GITHUB_SHA". (inferred, check the README)
  4. Run evalforge gate build/evalforge-artifact.json --policy examples/promptfoo_policy.json. (inferred, check the README)

Prompt for your agent

In the EvalForge repo (https://github.com/jsdhwfmax/EvalForge), convert a promptfoo results file at <promptfoo-results-path> with `evalforge import promptfoo <promptfoo-results-path> --output build/evalforge-artifact.json`, then run `evalforge gate build/evalforge-artifact.json --policy examples/promptfoo_policy.json`. Expected output is the gate verdict; verify the adapter accepted results schema 3.

Caveat. The promptfoo adapter is verified against promptfoo 0.122.2 and requires results schema 3, so other promptfoo versions may be rejected.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page