Outputs are invisible

I’m new to Github Actions so when I didn’t see my “outputs” listed in the output (even though I had tried to output them frequently via logging) I must have banged my head against the wall for hours trying to figure out what was going on.

I now understand they were always there, just hidden during output. It’d be great if during the default UI you could see the outputs SOMEWHERE.

1 Like

@aronchick,
By default, GitHub Actions does not automatically list all the outputs in a job to the logs.
However, you can easily view all the outputs of a step from the steps context. And view all the outputs of job from the needs context.
You just need to print the contexts to the logs.

Hi, can you say more? How would I differentiate if my script was broken (and did not output anything) or it output the items correctly but GitHub had hidden it? I get that I can throw another step in there to check output, but it’d be nice to see if GitHub had detected output and done something with it (rather than just silently swallowing that action).

@aronchick,
I found an way to let the outputs can be shown to the logs of the run, is enabling debug logging. From the debug logs, we can see more info about each step run, include the outputs.

For example, I have an action will generate an output,

  • Before enabling debug logging, the logs for this action in the workflow run looks as:
    result-1

  • After enabling debug logging, the logs for this action in the workflow run looks as:
    result-2

You can see after enabling debug logging, the logs will show the command that setup the output, and the result of the generated output (how to access this output).

Right, but this seems like a lot of work (e.g. i have to check in and fire off an entirely new build every time i want to check an output). I’m just asking for SOME indicator about what was output since GitHub is silently swallowing it right now.

@aronchick,
Okay, according to your said,

It’d be great if during the default UI you could see the outputs SOMEWHERE.

I think your question is more like a feature request. So I recommend you directly report a feature request here. That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions.