GitHub Community
Replies: 31 comments 1 reply
-
|
This is really important. Currently logs of composite actions looks like mess. Why no update on this yet? |
Beta Was this translation helpful? Give feedback.
-
|
This is my biggest annoyance with composite actions atm. I am more than happy for them not to even be subspaced, but each step could be right at the top level just like regular steps. After all it is a "composite" of steps. |
Beta Was this translation helpful? Give feedback.
-
|
Bumping this as well, agree with the rest of the folks |
Beta Was this translation helpful? Give feedback.
-
|
We would also greatly benefit from this |
Beta Was this translation helpful? Give feedback.
-
|
This could make things a lot nicer. Upvoting!! |
Beta Was this translation helpful? Give feedback.
-
|
We would love to have this |
Beta Was this translation helpful? Give feedback.
-
|
Bumping, this would be so helpful |
Beta Was this translation helpful? Give feedback.
-
|
This is a must-have. Right now, I'm forced to do some awkward stuff with multiple jobs (despite the fact it could all be in one job) in order to try to make the "build" steps visually distinct from the "test" steps. Otherwise, if the build fails, it looks like the test job failed unless you look super closely. |
Beta Was this translation helpful? Give feedback.
-
|
I moved one of my job steps to composite action, to solve another github actions limitation (to be able to skip jobs and still run dependent ones without needing to spam jobs with |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 still waiting for this |
Beta Was this translation helpful? Give feedback.
-
|
Damn! It's been nearly 2 years for this and still no response. |
Beta Was this translation helpful? Give feedback.
-
|
I would also love to see improved logging separation between steps within a composite action. |
Beta Was this translation helpful? Give feedback.
and others
-
See actions/runner#1311.
Describe the enhancement
Currently when using composite actions, the logs are all aggregated as if it was one big action.
This becomes quickly problematic to debug an error occurring in one step since we can't easily see when one step starts and one ends.
The best would be to have the "sub-steps" clearly displayed in the interface liked the steps are for a "normal" actions. We could settle for a text based split but it would not be ideal.
I feel this will be essential for
ifconditions to be introduced (issue actions/runner#834), otherwise it will be a mess to try to debug which steps ran and which were skipped.Additional information
Here is what it could look like:
Beta Was this translation helpful? Give feedback.
All reactions