test(eval): guard workspace path override compatibility#1535
Merged
Conversation
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.
Summary
--workspace-pathremains a supported way to point AgentV at an already prepared workspace and skip AgentV-owned materialization. This PR adds regression coverage for both the public CLI shorthand (agentv eval <file> --workspace-path <dir>) and the core setup path that must reuse the supplied directory without cloning repos into it.Validation
bun --filter @agentv/core build && bun --filter @agentv/sdk buildbun test apps/cli/test/eval.integration.test.tsbun test packages/core/test/evaluation/workspace/setup.test.tsbun apps/cli/src/cli.ts eval run --help | rg -- '--workspace-path|--workspace-mode'bun run typecheckbun run lint