Are public packages from a private repository free of storage/bandwidth quotas #195271
-
🏷️ Discussion TypeQuestion BodyThe GitHub Packages billing docs state:
We have a private repository that publishes public container images to GHCR. Which billing rule applies — "free for public packages", or the storage/bandwidth quota for "private repositories"? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment · 2 replies
-
|
According to GitHub's billing policies, the rule that applies to your situation is "free for public packages." GitHub Packages billing depends entirely on the visibility of the package itself, rather than the repository it originates from. Since you are publishing public container images, as long as the package visibility is set to 'Public', it falls under the free tier. This means it will not consume the storage or bandwidth quota allocated to your private repository. In short, you can keep your source code secure in a private repository while distributing the resulting images publicly at absolutely no extra cost. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I think the linked billing docs could make the wording more precise to avoid confusion. |
Beta Was this translation helpful? Give feedback.
-
|
thanks and i am making a nothour game on roblx |
Beta Was this translation helpful? Give feedback.
According to GitHub's billing policies, the rule that applies to your situation is "free for public packages."
GitHub Packages billing depends entirely on the visibility of the package itself, rather than the repository it originates from.
Since you are publishing public container images, as long as the package visibility is set to 'Public', it falls under the free tier. This means it will not consume the storage or bandwidth quota allocated to your private repository.
In short, you can keep your source code secure in a private repository while distributing the resulting images publicly at absolutely no extra cost.