Skip to content

Clarify custom image storage billing in Actions docs#43370

Closed
austenstone wants to merge 1 commit intogithub:mainfrom
austenstone:austen/custom-image-storage-billing
Closed

Clarify custom image storage billing in Actions docs#43370
austenstone wants to merge 1 commit intogithub:mainfrom
austenstone:austen/custom-image-storage-billing

Conversation

@austenstone
Copy link
Member

GitHub Copilot generated this pull request.

Summary

  • add a canonical billing explanation for custom image storage in the GitHub Actions billing docs
  • trim the custom images task doc to a shorter summary that links to the billing source of truth
  • clarify related runner pricing and hosted runner reference copy

Validation

  • checked editor diagnostics for all changed files
  • attempted to run content lint, but the local environment is missing ()

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 16, 2026
@github-actions
Copy link
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
actions/concepts/runners/github-hosted-runners.md fpt
ghec
ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14
actions/how-tos/manage-runners/larger-runners/use-custom-images.md fpt
ghec
fpt
ghec
billing/concepts/product-billing/github-actions.md fpt
ghec
fpt
ghec
billing/reference/actions-runner-pricing.md fpt
ghec
ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@austenstone austenstone marked this pull request as ready for review March 16, 2026 01:05
Copilot AI review requested due to automatic review settings March 16, 2026 01:05
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates billing documentation to clarify how storage costs apply to Actions custom images used with larger runners, and adds a dedicated section describing the custom image storage accrual model.

Changes:

  • Adds a new “Custom image storage” section to the GitHub Actions billing concepts page with an accrual explanation and examples.
  • Updates runner pricing and runner concepts docs to reference the new anchored billing section for custom image storage.
  • Adds billing/storage guidance to the “Use custom images” larger runners how-to.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
content/billing/reference/actions-runner-pricing.md Expands the custom images pricing note to include separate storage billing and links to the new section.
content/billing/concepts/product-billing/github-actions.md Introduces a new “Custom image storage” section explaining GB-Hours accrual and retention impact.
content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md Adds a “Billing and storage for custom images” section and points readers to billing + retention policy docs.
content/actions/concepts/runners/github-hosted-runners.md Adjusts the billing link to point directly to the new “Custom image storage” anchor.

You can also share your feedback on Copilot code review. Take the survey.

* Included minutes cannot be used for {% data variables.actions.hosted_runner %}s.
* The {% data variables.actions.hosted_runner %}s are not free for public repositories.
* Custom images can only be used with larger runners and are billed at the same per-minute rates as those runners.
* Custom images can only be used with larger runners. Jobs that use custom images are billed at the same per-minute rates as those runners, and storage for custom images is billed separately through {% data variables.product.prodname_actions %} storage based on the amount of stored image data over time. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-actions#custom-image-storage).
Custom images can include repository code, container images, binaries, certificates, and other dependencies to create a consistent build environment across workflows. This helps you gain control over your supply chain. They help reduce setup time, improve build performance, and strengthen security by reducing the surface attack vector on your images. Administrators can also apply policies to manage image versions, retention, and age to meet organizational security and compliance requirements.

Custom images can only be used with larger runners and are billed at the same per-minute rates as those runners. Storage for custom images is billed and metered through {% data variables.product.prodname_actions %} storage. For more information about billing, see [AUTOTITLE](/billing/concepts/product-billing/github-actions).
Custom images can only be used with larger runners and are billed at the same per-minute rates as those runners. Storage for custom images is billed and metered through {% data variables.product.prodname_actions %} storage. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-actions#custom-image-storage).
@austenstone
Copy link
Member Author

Closing this PR because the change is being tracked in the private source repository instead: github/docs-internal#60231.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants