chore: refresh eval results - #283
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mattrossman
added a commit
that referenced
this pull request
Sep 11, 2026
This change reorganizes all evals under per-suite folders e.g. `evals/<suite>/<id>/` which replaces the `suite:` frontmatter, so CODEOWNERS can scope by path. It then gives the docs team their own `docs` eval suite so they can add and refresh evals on their own cadence, per the [meeting notes](https://app.notion.com/p/supabase/Docs-evals-3d75004b775f818eab9bd8f309615eeb) and [Slack](https://supabase.slack.com/archives/C051L8U2EJF/p1789067654536789). Docs evals run on the Luna [no-skills experiment only](https://supabase.slack.com/archives/C051L8U2EJF/p1789075644655989). The new `CODEOWNERS` lists AI team as default codeowner, with docs team as owner for the `evals/docs/` and its results `.json `file. > (Diff note: everything under `evals/` is a `git mv`, 50 of which also lose a `suite:` frontmatter line. Real changes are the 11 files outside it.) ## How to review Dry run to see the list of experiment x evals that run under the docs suite: ```bash pnpm eval:dry -- --suite docs --experiment-suite docs ``` Which produces the full set of docs runs: ```bash 1 experiment(s), 3 eval(s), runs=1, timeout=720s, concurrency=1 PLAN codex-gpt-5.6-luna-no-skills x build-docs-001-homepage-quickstart stage=build suite=docs mode=local-stack runtime=local-stack model=gpt-5.6-luna PLAN codex-gpt-5.6-luna-no-skills x build-docs-002-rls-guide stage=build suite=docs mode=local-stack runtime=local-stack model=gpt-5.6-luna PLAN codex-gpt-5.6-luna-no-skills x build-docs-003-api-keys-guide stage=build suite=docs mode=local-stack runtime=local-stack model=gpt-5.6-luna ``` For more concrete evidence of the new docs results structure, see this sample PR #283 which was [generated](#282 (comment)) by the refresh workflow on the current PR. > Note the generated results PR branch also now includes the suite so concurrent dispatches from both teams don't overwrite each other. See also a new [Docs evals](https://github.com/supabase/evals/blob/82c705029a1157cdf9d6056ff9da5091ae65bd00/CONTRIBUTING.md#docs-evals) section of the contributing guide to explain common evals workflows to docs contributors. ## After merge Flip [main: review required](https://github.com/supabase/evals/settings/rules/18775100) to require code owner review with 1 approval and drop the `ai` team required-reviewers entry, so CODEOWNERS decides who approves docs PRs. Closes AI-1203
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refreshes
apps/web/src/data/eval-results.jsonfrom the latest automated eval run.