Closed kobalicek closed 1 year ago
Yes, that make sense. I've been thinking about this as well. A feature flag is not necessary. No information will be removed. It's just not visible by default.
Now everything is hidden behind output groups except for the actual run command. I didn't bother in doing a more fine grained change.
Thanks, this is amazing!
At the moment when a VM is run, there is a lot of messages, which are then combined with messages produced by the run script. GH actions provides a way how to group these messages by using
::group::
prefix during logging.My question is whether it would be possible to use such groups to make the run script output easier to find. I have added a small screenshot from a workflow run where the content in the red rectangle is the actual code that runs in the VM (basically the content I'm most interested in), whereas all the output outside is from VM init/shutdown.
I would not mind having this feature optional, behind a flag, for example.