question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

sections marked with `::group::{title}` should be able to request to not be collapsed

See original GitHub issue

I’m sorry if this is the wrong place to request additional workflow commands, but I’m not sure where to put this.

Using the ::group::{title} and ::endgroup:: commands are useful to collapse verbose output or add section “headers” to the logs. However, sometimes after creating the group it is discovered that the group should not be collapsed and that it should be shown to the user.

A good example of this would be after a test fails:

Screenshot from 2021-04-02 11-57-02

Obviously a user who has experience with the GitHub actions UI and also tox in this situation, would know they should expand the grouped log lines above. In this simple example it is rather obvious which lines should be expanded, but this may not always be the case if the logs are long or the grouping is inconsistent or poorly named.

For this use case it would be great if the workflow author could write something like ::group-expand:: in order to force the UI to expand the log lines. This command could be valid until the ::endgroup:: command is issued, and as it is unlikely that a workflow author would need to change their mind about to show or not to show the group so there would not need to be a ::group-collapse:: command.

If this is not possible, an inferior solution would be to have a ::cancelgroup:: command which would act as the ::endgroup:: command, but remove any log grouping which was previously requested.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:4
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
terencehonlescommented, May 3, 2023

It means that this was the wrong place and it looks like the place I was told to report it in has now disappeared …so basically this is going to /dev/null 🤷

1reaction
P1119r1mcommented, Feb 13, 2023

I was unable to find neither feature request:

nor:

Can someone share the current status of this request? It is marked as “Closed”. What does it means? Is it closed, or resolved?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Expand/collapse section in UITableView in iOS
this initially worked for me when i had just one section, but as soon as i had more, i get the "invalid update...
Read more >
How to prevent section collapsing when there are missing ...
Hi guys. The user has a screen where are multiple collapsed sections and each section has a set of required fields. Sometimes user...
Read more >
Keep collapsed sections collapsed when saved under " ...
I have not found a way to collapse sections at all, even if the view does not save as the default view -...
Read more >
Collapsed sections in mobile sidebar don't expand when ...
i think my users will grow to like it, especially with the manually expanding and collapsing sections and the menu itself. i think...
Read more >
Sharpoint Collapsing sections -> call by URL
What I'm trying to set up: I have a page (like an FAQ page) with many sections which are by default collapsed. In...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found