As per the issue title, currently the GHA will use .venv (uv venv's default) in the working-directory. It would be nice if we could specify the custom venv name (e.g., venv) as the GHA input. Then developers can control their venv content more explicitly. Or we can add ${{ working-directory }}/.venv as the step output to manage the GHA script in a more programmatic way (e.g., steps.setup-uv.outputs.uv-venv).
Reactions are currently unavailable
As per the issue title, currently the GHA will use .venv (uv venv's default) in the working-directory. It would be nice if we could specify the custom venv name (e.g., venv) as the GHA input. Then developers can control their venv content more explicitly. Or we can add ${{ working-directory }}/.venv as the step output to manage the GHA script in a more programmatic way (e.g., steps.setup-uv.outputs.uv-venv).