From a76ea4932f4a8b57a91bc252652d82ec33ba5b91 Mon Sep 17 00:00:00 2001 From: Scott Lowe Date: Tue, 13 Oct 2026 21:16:00 -0700 Subject: [PATCH] VAP15-77 docs: rename the PR check status to Vapi Simulations Follows VapiAI/gitops#82, which renames the status the gitops PR check posts from Vapi Evals to Vapi Simulations. Co-Authored-By: Claude Opus 5.5 --- fern/config-as-code.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fern/config-as-code.mdx b/fern/config-as-code.mdx index 00ef8fcd4..f06db1a15 100644 --- a/fern/config-as-code.mdx +++ b/fern/config-as-code.mdx @@ -35,7 +35,7 @@ Config as code keeps your Vapi configuration in files under version control inst - **Safe sync.** `npm run apply` pulls the latest platform state before it pushes, so edits made in the dashboard aren't silently overwritten. Every deploy saves a snapshot you can roll back to. - **Readable references.** Files refer to each other by name (`toolIds: [lookup-patient]`). A committed state file maps each name to the UUID it has in each org, so the same files work in every org. - **Any number of orgs.** Each org is a folder. Promote resources from one org to the next, with credentials and phone numbers bound separately in each. -- **Tests on every pull request.** Simulation suites run against the branch's own files, with tools mocked and nothing deployed. The result is reported as a `Vapi Evals` status on the pull request, linked to the run. +- **Tests on every pull request.** Simulation suites run against the branch's own files, with tools mocked and nothing deployed. The result is reported as a `Vapi Simulations` status on the pull request, linked to the run. - **Ready for coding agents.** `AGENTS.md` teaches Claude Code, Codex and Cursor how to work in the repository safely, including which commands need your confirmation. ## Get started @@ -141,7 +141,7 @@ See the [promotion guide](https://github.com/VapiAI/gitops/blob/main/docs/guides Every pull request runs a **Validate resources** check, which validates each org's files offline, without secrets. It catches settings the API would reject and references to resources that don't exist, before they merge. -Simulation suites in the repository can also run on every pull request, against the branch's own files. Nothing is deployed, and tool calls get mocked results. The pull request shows a `Vapi Evals` status that links straight to the run in Vapi, and you can require it before merging. Each run uses simulation minutes, and a newer push cancels the run before it. +Simulation suites in the repository can also run on every pull request, against the branch's own files. Nothing is deployed, and tool calls get mocked results. The pull request shows a `Vapi Simulations` status that links straight to the run in Vapi, and you can require it before merging. Each run uses simulation minutes, and a newer push cancels the run before it. See the [PR checks guide](https://github.com/VapiAI/gitops/blob/main/docs/guides/pr-checks.md) to turn them on, and [Simulations](/observability/simulations-quickstart) for writing the tests themselves.