-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using ::group:: to distinguish between steps? #49
Comments
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. |
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 4, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 5, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 5, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 5, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 5, 2023
jacob-carlborg
added a commit
that referenced
this issue
Mar 5, 2023
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! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: