Austin Hallett

I am guessing the expected use case is something like the following... ```yaml hello-from-container: runs-on: ubuntu-latest steps: - id: setup name: setup jfrog uses: jfrog/setup-jfrog-cli@v4 with: ... - name: authenticate...

@williammartin Maybe I am misunderstanding your rec. I set `GH_DEBUG: api` at the step-level in the workflow, but I am not seeing any logs at all.

Correct. Job dispatched, but no logs for that step at all.

from the workflow ui ``` gh workflow run smoke-test.yml --repo my-org/my-repo --ref master -f version="0.0.0" shell: sh -e {0} env: GH_TOKEN: *** GH_DEBUG: api ``` no logs

Right, this is a private repo. Let me see if I can reproduce using a new public repo. I will follow up here afterwards

note even when running manually I am not getting debug info ``` ➜ GH_DEBUG=api gh workflow run fake.yml --repo my-org/my-repo --ref master -f version=0.0.0 could not find any workflows named...

It is installed in the docker image we are running in our build pipelines. It's an Ubuntu Jammy-based container. Installed via `apt-get`. The image is built weekly

- [x] Updated gh CLI ``` * Request at 2025-04-29 18:31:33.032831874 +0000 UTC m=+0.049374454 * Request to https://api.github.com/repos/my-org/my-repo/actions/workflows/smoke-test.yml > GET /repos/my-org/my-repo/actions/workflows/smoke-test.yml HTTP/1.1 > Host: api.github.com > Accept: application/vnd.github.merge-info-preview+json, application/vnd.github.nebula-preview >...

Note the second job was cancelled (in the case of both screenshots) because I did not want to run it twice