feat(results): support global per-project results config#1296
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
7d24cdd
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2e666445.agentv.pages.dev |
| Branch Preview URL: | https://feature-agentv-global-result.agentv.pages.dev |
46fcf1e to
7d24cdd
Compare
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
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.
Summary
Registered Dashboard projects can now use machine-local results repos from
$AGENTV_HOME/config.yamlwithout editing each source repo's.agentv/config.yaml.results_by_projectmaps project IDs to the existingResultsConfigshape, while project-localresultsstill wins and top-level globalresultsremains the fallback.Dashboard remote status, sync, run listing, and remote artifact materialization now carry the registered project id through the shared results helpers. Local eval auto-push also resolves the registered project containing the cwd, so evals launched from a registered source repo use the matching global results mapping.
Evidence
Red on
origin/main, same registered project plus globalresults_by_projectonly:{"configured":false,"available":false,"repo":"","local_dir":"","run_count":0}Green on this branch:
{"configured":true,"available":true,"repo":"EntityProcess/agentv-examples-eval-results","path":"/home/entity/projects/EntityProcess/agentv-examples-eval-results","auto_push":true,"branch_prefix":"eval-results","local_dir":"/home/entity/projects/EntityProcess/agentv-examples-eval-results","run_count":3}Verification
bun test packages/core/test/evaluation/loaders/config-loader.test.tsbun test ./test/commands/results/serve.test.tsfromapps/clibun run typecheckbun run lintbun run build