Feature request
It would be useful to have a quiet (or verbosity) input that either suppresses non-error output or wraps the action's log lines inside a GitHub Actions log group (::group::/::endgroup::).
Motivation
When setup-uv is embedded inside a composite action alongside several other steps, its output can dominate the log. Other steps in the same composite already use ::group:: to fold their output, but there is no way to do the same for a uses: action step — GitHub Actions only allows ::group:: inside run: shells. The only current workaround is to replace the action with a manual run: step, which sacrifices the caching and convenience it provides.
Proposed behaviour
Add an optional input, e.g.:
- uses: astral-sh/setup-uv@...
with:
quiet: "true" # wraps all output in ::group:: or suppresses non-error lines
Alternatively, the action could unconditionally wrap its own output in a log group (collapsed by default), similar to how many other setup actions behave.
Example context
- name: Install uv
uses: astral-sh/setup-uv@5a095e7a2014a4212f075830d4f7277575a9d098 # v7
with:
version: ${{ steps.versions.outputs.uv }}
python-version: ${{ steps.versions.outputs.python }}
activate-environment: "true"
quiet: "true" # desired, not currently supported
Feature request
It would be useful to have a
quiet(orverbosity) input that either suppresses non-error output or wraps the action's log lines inside a GitHub Actions log group (::group::/::endgroup::).Motivation
When
setup-uvis embedded inside a composite action alongside several other steps, its output can dominate the log. Other steps in the same composite already use::group::to fold their output, but there is no way to do the same for auses:action step — GitHub Actions only allows::group::insiderun:shells. The only current workaround is to replace the action with a manualrun:step, which sacrifices the caching and convenience it provides.Proposed behaviour
Add an optional input, e.g.:
Alternatively, the action could unconditionally wrap its own output in a log group (collapsed by default), similar to how many other setup actions behave.
Example context