show name of steps defined in composite actions on browser UI

[yamy1114]

The composite actions is a very convenient function, and we create many composite actions and utilize them.

For more convenient use, I would like to request an improvement of browser UI.

Now, we can define name of steps in composite actions, but the name is not shown in browser UI.
If the name of steps is shown and we can expand log by clicking the name same as normal step, we can get the summary of jobs more easily and quickly.

I know that we can show customized summary in browser UI by defining ::group as workflow command,
but I would not like to write ::group every steps in composite actions.

Could you show name of steps in composite actions on browser UI. 🙏

[ethomson]

This is helpful feedback, @yamy1114, I appreciate it. We'll make sure that this is on the backlog.

[yamy1114]

thank you! I'm looking forward to implementing the function.

[ghost]

There is a practical disadvantage of composite actions being shown in one 'group' in the UI - I can't get a summary of how long each part takes, easily.

I tried using echo ::group::{name} - but that seems to not work across steps anyway!

[anthonwellsjo]

Any news on this? I'd love to have this aswell...

[phuongthuan]

Any updates on this one? Is this still in backlog?

[bschilder]

I'd also find this feature extremely helpful! It makes the output of long custom workflows comprised of other actions much more navigable. It also helps pinpoint exactly which step the workflow may have failed at.

[hemachandsai]

+1

[gorkemgoknar]

Please at least make it parameter that we can show steps called inside composite action (we are using for common local composite action)
+1

[NoamGaash]

+1

[hex0cter]

+1

[Epgor]

+1

[pgoltsev]

+1

[arjun-menon]

+1

Similar:

• Composite actions steps logs should be clearly separated actions/runner#1311
  • https://github.com/orgs/community/discussions/21276

[arafatiqbal]

+1

[clFaster]

+1 https://github.com/orgs/community/discussions/21276

[KaloyanTanev]

+1

[rahulshrivastava-eaton]

still waiting for this

[LittleGreenYoda42]

+1

[dpotyralski]

+1

[Drowze]

This also affects how Datadog traces our GitHub workflows (context: https://docs.datadoghq.com/continuous_integration/pipelines/), example:

In the screenshot above:action-parallel-test is a composite action which is reused in a few of our private repositories - would be nice to have a breakdown of each step - so that Datadog could trace that separately as well.

[AlekSi]

See also actions/runner#1877

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[nickfollett]

+1

[wmcnamee-coreweave]

+1

[herve-er]

+1

[hiteshsahu]

Its 2025. and this issue is not yet fixed.

Only work around for this to add logs that can help differentiate blocks of steps. I know this is not the same but this is the only thing that is close enough:

 shell: bash
      run: |
          ###---  📜 Download Project file: ${{ inputs.file_name }} from ${{ inputs.s3-link }}  ---###

[cjbhaines]

+1

[raphaaugustosilva]

+1

[ramonrrp]

+1

[ericsciple]

Hi everyone 👋

I've posted a detailed update on this in #21276 with mockups and questions:

Proposal: Collapsible regions for nested steps in the log panel

We would love your feedback, especially on whether collapsed-by-default works for you, and whether log panel visibility is sufficient or if you need sidebar entries too.

— The GitHub Actions Team