Readable Nested Actions Check Names

[Jacobfaib]

Select Topic Area

Product Feedback

Body

Github automatically generates the name of each "job" based on the hierarchical path of actions. If action Foo calls action Bar calls action Baz, then the resulting job name is Foo / Bar / Baz.

This gets worse if any of these is a "matrix" job, in which case the exact parameters of the matrix are also added in parentheses: Foo (a, b) / Bar (c, d) / Baz (e, f).

For any moderately complex CI/CD pipeline, this gets out of hand very quickly, very often resulting in duplicate information as matrix parameters are passed through:

Is there any way to make these less verbose?

---

There is a workaround I have found, by making the name: field in jobs some kind of "dynamic" string (static names don't work¹):

jobs:
  some_long_job_name:
    name: _ ${{ '' }} # hack

Which looks... okay...:

But then this break the hierarchical view of the jobs in the summary view:

New:

vs old:

Footnotes

1. 1. It cannot be all whitespace or empty (e.g. just '' or ${{ '' }}), because then Github just uses the default naming scheme (job/step name + list of arguments)
   2. If it's a matrix job, it cannot be a "static" name, because then Github still adds the matrix parameters: my_static_name (a, b, c). This is why we fool github by using ${{ '' }}. Because it's an expression, Github presumably thinks its dynamic, and hence doesn't add the default.
   3. It needs to be done every. step. of. the. way. because of course why would anyone at Github think that the top-level action should be able to control the name...
   ↩

[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. ⭐