The Repository Actions Runners List is in Public Beta

[tuves]

The Repository Actions Runners List is generally available

We're excited to announce the latest addition to GitHub Actions: the Repository Actions Runners List! As we continuously strive to improve your development and CI/CD workflows, this new feature aims to make your GitHub Actions experience smoother and more intuitive.

Key features of the Repository Actions Runners List:
Comprehensive Runner Overview: All available runners, be it Standard GitHub-hosted, Larger GitHub-hosted (for faster builds), Self-hosted, or Scale-sets, are now visible in a single pane.

Swift Runner Label Access: Those with repo:write access don't have to sift through internal documentation or ping a Repo admin or an Organization owner for runner label names anymore. You can now quickly view and copy runner labels, ensuring you're always picking the right runner for your workflows.

🔍 How to Access:

1. Go to your repository main page.
2. Click on the "Actions" tab.
3. In the left sidebar under "Management", you'll find the "Runners" option.
4. Explore, copy labels, and even create new runners if you're an Enterprise or Organization owner.

Who gets to use it?:

• Users with Free and Pro Personal Accounts.
• Free Organizations.
• Paid Organizations under Team and GitHub Enterprise Cloud plans.
  Note: The feature is currently not available for GitHub Enterprise Server and Legacy plan users.

We Value Your Feedback!

Community feedback is pivotal in shaping the trajectory of our features. As you explore the new Repository Actions Runners List, we'd love to hear about your experiences, suggestions, and any potential improvements. Join the discussion below and help us make GitHub even better!

[BenjaminYde]

We have repo's with self hosted runners assigned to it (in "Settings/Actions/Runners"), but we don't see then in the "Actions" tab of the repo?
Don't know if this is normal? We have a paid team plan.

[D1M1TR10S]

Hey @BenjaminYde. This feature is being released on a gradual rollout. You should see it appear in your repos in the coming weeks. Thanks for the feedback!

[DirkLachowski]

Don‘t see them in an org with a payed team plan. Slow rollout or something wrong?

[D1M1TR10S]

Hey @DirkLachowski. That's correct. We're doing a gradual rollout for this feature, which is currently in public beta. The plan is to make it available to all eligible users in the coming weeks.

[janpio]

Would be good to mention that in the blog post which makes it sounds like this should be available now for everyone besides "users in Organizations on the GitHub Enterprise Server and Legacy plans, or Enterprise Managed Users".

[D1M1TR10S]

Just updated the Changelog post @janpio. Good callout. 🙂

[jdesulme]

I see that this is getting enabled for GitHub Enterprise Cloud but doesn't seem to be planned for those using Enterprise Managed Users. Why is that case and will EMUs eventually get in down the line?

[D1M1TR10S]

Good question @jdesulme. As this point, the feature is focused on certain plans to gather initial user feedback and ensure everything is working as expected.

This feature was implemented by the Growth team here at GitHub as an experimental beta. I'll make sure to forward your request to the Actions team for consideration. Thank you for bringing this up! 👍

[nizzantalon]

Can you add the status of each runner, or even better the specific active job?
This is definitely a step in the right direction but having the status would greatly increase the visibility for the team.

[D1M1TR10S]

Thanks for the feedback, @nizzantalon. We're actively compiling suggestions for future updates. Just added your request to the list!

[croydondias]

Can you add the cpu/mem/disk details for the self hosted runners as you've done to the GitHub hosted runners?

As a team that only uses various types of self hosted compute, this would give our users more transparency.

[D1M1TR10S]

Hi @croydondias. So this feature was shipped by the growth team here, and we focus on experimental beta features. I'll be sure to forward your request along to the Actions team though. Thank you for the feedback!

[nizzantalon]

Another issue: clicking "..."-> "Copy label" will copy the runner NAME and not the LABEL(s).

[D1M1TR10S]

So this piece was intentional @nizzantalon. The runner name is the most common way that users are referencing runners to use them in jobs. Some runners have a long list of custom labels and/or runner group labels, and the goal here was to keep the UX simple and easy to understand.

Are there specific cases where you want to access labels aside from the runner's name?

[nizzantalon]

Then the button should indicate "copy name" and not label.

[D1M1TR10S]

So the runner name is technically a label as well. I can see how we could make this more apparent though. Thank you for the feedback!

[BenjaminYde]

What are the future plans for the Actions & Actions.Runners tab?
Do we need to expect other features coming in the near future?
Currently there's just a list with runners.
I mean things like:

• Github Actions Dashboard: https://github.com/orgs/community/discussions/60611
• Github Workflow management: https://github.com/orgs/community/discussions/63316
• Github Runner management...
• CI CD user roles...
• Runner statistics...
• Add runners to groups for specific teams...
• ...

[D1M1TR10S]

Here's a link to our public roadmap with a filter set for Actions @BenjaminYde

I've documented your requests and I'll be sure to share them with the team!

[etreskovskis-ms]

Is the Repository Actions Runners list (self-hosted) available through API call?

[D1M1TR10S]

Hi @etreskovskis-ms. You can access a list of Self-hosted runners via API at the organization level, and specify the scope to the repo in question. Here are the docs on how to do that.

Keep in mind that "Authenticated users must have admin access to repositories or organizations, or the manage_runners:enterprise scope for enterprises, to use these endpoints." If your goal is use the API to provide runners info to non-admins (similar to the Repo Runners List), then you would need to store this information in a database and make it available to non-admins using your own API or web app.

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