Skip to content
Discussion options

You must be logged in to vote

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.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@rophy
Comment options

@abdullahasad3670-ops
Comment options

Answer selected by rophy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Packages Host your dependencies, libraries, and production-ready code, right from your repository Question Ask and answer questions about GitHub features and usage source:ui Discussions created via Community GitHub templates
3 participants