GH Packages Pricing and Install with GITHUB_TOKEN

From what I’ve read in some other questions is that its not possible to use GITHUB_TOKEN to install packages from other repos, and you should instead use a personal token.

In the pricing table on GH packages it says: “Data transfer out within Actions” = “Unlimited”  and in the about page of github packages says: “When you create a GitHub Actions workflow, you can use the GITHUB_TOKEN to publish and install packages in GitHub Packages without needing to store and manage a personal access token.”

My question is, how is github going to price correctly the installs if we’re not able to use the GITHUB_TOKEN to install our GH packages from GH Actions?

If this doesn’t work, then that pricing table feels a bit like false advertisement.  

Hi @canastro ,

If the package is on the other repo, GITHUB_TOKEN doesn’t have enough access to pull the package and used to install it, then personal access token is needed. This will require payment.

If you directly push and pull your packages from within your workflow, GITHUB_TOKEN is permission enough, it should be unlimited. 

You can refer to similar ticket here for more details.

Thanks.

But I don’t think it makes sense to pay for installs on packages within the same organization. Thats not clear in the pricing and anywhere in the documentation.

How does GH Packages identifies if a install came from GH Actions? Is by checking the token used? 

The only way that we can use GITHUB_TOKEN to install from GH Packages is with a mono-repo approach?

Hi @canastro ,

The only way that we can use GITHUB_TOKEN to install from GH Packages is with a mono-repo approach?

>> it’s accurate.

How does GH Packages identifies if a install came from GH Actions? Is by checking the token used? 

>>It’s based on ip-address, hosted VM’s have known ip range.

More details please check official link:

https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages

Thanks.

1 Like