Feature: Add runner group to queued worflow hook

[gabriel-samfira]

Select Topic Area

Product Feedback

Body

Hi,

Currently the runner group field is not being sent as part of the queued workflow hook. If I define a workflow with the following runs-on definition:

runs-on:
  group: my-runner-group
  labels: ["large", "self-hosted"]

in the queued workflow hook we see the labels but not the runner group. This makes it difficult to schedule the creation of a self hosted runner in the proper runner group. I realize there are scale sets now, but it would be great to still make use of labels and runner groups without brute forcing the github API to figure out which group a runner should be a part of.

The runner group only shows up in in_progress workflow jobs, after a runner picked up the job.

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