Question

A GitHub Enterprise Cloud administrator notices the monthly invoice has grown significantly beyond the predictable per-seat license cost. Investigation shows heavy usage of GitHub Actions minutes for private repositories and large amounts of GitHub Packages storage. The finance team wants to understand which parts of the bill are fixed versus variable so they can forecast future costs. How should the administrator explain the billing structure for these consumption-based services?

Accepted Answer

Actions minutes and Packages storage are billed on a usage-based (metered) model beyond the plan's included allotments, separate from the fixed per-user license seats.

Answer

All Actions and Packages usage is bundled into the per-user license price, so the overage must be caused by additional purchased seats rather than usage.

Answer

Actions and Packages are billed only annually as part of the enterprise agreement true-up and cannot be tracked or forecasted monthly.

Answer

Actions minutes for private repositories are always free; only Packages storage is metered, so the entire overage stems from storage alone.