Skip to content

feat: create workspace setup and teardown for each eval case #177

@christso

Description

@christso

Currently evals require a VS Code workspace setup already. We should setup a temporary workspace on demand. We can cache the workspace instead of clone the repo for each eval. So, after each eval, we have a teardown method than cleans up files added during the eval.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions