feat: add venv-path input for custom virtual environment location

Allow users to specify a custom path for the virtual environment when
using activate-environment. This is useful for CI workflows that need
to create isolated venvs outside the working directory (e.g., in
$RUNNER_TEMP) to avoid conflicts with project-level configurations.

When venv-path is not specified, the default behavior remains unchanged
(.venv in the working directory).
This commit is contained in:
Eli Uriegas 2026-01-20 13:15:57 -08:00
parent 9cfd029643
commit c19391797c
6 changed files with 89 additions and 10 deletions

View file

@ -15,6 +15,9 @@ inputs:
activate-environment:
description: "Use uv venv to activate a venv ready to be used by later steps. "
default: "false"
venv-path:
description: "Custom path for the virtual environment when using activate-environment. Defaults to '.venv' in the working directory."
default: ""
working-directory:
description: "The directory to execute all commands in and look for files such as pyproject.toml"
default: ${{ github.workspace }}