Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-minute rates for standard runners doesn't hint that Linux-2 core can be arm runners #36648

Open
1 task done
jsoref opened this issue Mar 6, 2025 · 3 comments
Open
1 task done
Labels
content This issue or pull request belongs to the Docs Content team triage Do not begin working on this issue until triaged by the team

Comments

@jsoref
Copy link
Contributor

jsoref commented Mar 6, 2025

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates-for-standard-runners

What part(s) of the article would you like to see updated?

  • Linux 2-core should gain a parenthetical, probably (Intel or Arm), but possibly something else similar to:
  • macOS 3-core or 4-core (M1 or Intel)

Additional information

Even though I've probably read a whole bunch of blogs about Linux arm runners, and talked about it with people, I went to this pricing page to try to figure out if I can run a linux arm runner for free and if so how.

I came away from this page thinking that Linux Arm runners were only available in Large runners and that Large runners were paid only.


It is apparently a thing, as there's a changelog entry for it:

@jsoref jsoref added the content This issue or pull request belongs to the Docs Content team label Mar 6, 2025
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 6, 2025
@jc-clark
Copy link
Contributor

jc-clark commented Mar 6, 2025

Hey @jsoref! Thanks for the issues.

I agree with your take in #36649, and I definitely think there are some improvements we can make in that article to make the connection to the standard GitHub-hosted runners for public repos clearer. I'll make a comment on that issue with some follow up suggestions.

For this issue though, I don't think we need to update the per-minute rates with a parenthetical. These per-minute rates apply to private repositories. And under Standard GitHub-hosted runners for private repositories, x64 is the only architecture listed. So updating the list in the way you're suggesting wouldn't be accurate.

Perhaps there's an opportunity to make that nuance a bit clearer though. What do you think about adding some text like this under the Per-minute rates for standard runners header?

Per-minute rates for standard runners apply to usage in private repositories that exceeds the included minutes for your plan. For information about free standard runner availability in public repositories, see Standard GitHub-hosted runners for public repositories.

@jsoref
Copy link
Contributor Author

jsoref commented Mar 6, 2025

I'm not looking for per-minute rates, i'm looking for a reference to arm (for Linux). There's already a hidden reference to arm for macOS (in the form of M1, which is a frustrating codeword). I don't care about the rates. I need to know:

  1. Are they available for free for public repositories (with my current hat, I don't want to pay, and if they require setting up a large runner, I'm going to run away)
  2. How to do that -- which means I eventually need something to link to the page that tells me the names of the "standard" arm runners.

@jc-clark
Copy link
Contributor

  1. In the changelog you posted, it says:

    Now in public preview, Linux arm64 hosted runners are available for free in public repositories.

  2. To use them, use ubuntu-24.04-arm or ubuntu-22.04-arm in your workflows. This is in the standard GitHub-hosted runners for public repos table.

I don't think we need to update any docs for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team triage Do not begin working on this issue until triaged by the team
Projects
None yet
Development

No branches or pull requests

2 participants