Add ability to do group-expanded to log-order for better CI readability in Github Actions

[runspired]

Which project is this feature idea for?

Turborepo

Describe the feature you'd like to request

see title

Describe the solution you'd like

see title

Describe alternatives you've considered

choosing chaos with --log-order=stream

_TURBO-1857

[anthonyshew]

Could you provide more details? How is this different from --log-order=grouped?

[runspired]

@anthonyshew log order grouped collapses all groups, makes it impossible to find which groups have failures in them.

An alternative here is to make --log-order=grouped expand any groups that have failures in them

[tknickman]

@runspired groups with failures are listed at the end of the run, but agreed - runs with failures should be expanded by default!

[maschwenk]

I guess in terms of feasibility:

https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#grouping-log-lines unclear if the expandability state is actually controllable?

I wonder if an alternative would be to pin failures to the bottom or something? Or restate them in a summary like Jest does? I know y'all have the --summary but obviously that's not super human readable.

[mehulkar]

Since we're buffering the output until the task is done, we can just omit the group start/end markers for NZE tasks