Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Actions doesn't work with private repositories #19

Closed
eliheuer opened this issue Jul 9, 2021 · 2 comments
Closed

GitHub Actions doesn't work with private repositories #19

eliheuer opened this issue Jul 9, 2021 · 2 comments

Comments

@eliheuer
Copy link
Contributor

eliheuer commented Jul 9, 2021

I'm working on some fonts hosted in a private GitHub repository, I set up the Google Font Unified Font Repository for that repo, but I get the following error in the Actions tab of the GitHub page:

GitHub Actions workflows can't be executed on this repository.
The billing plan for ********** does not include access to GitHub Actions. Please contact the organization owner or billing manager for questions about the current billing plan.

More info about this from GitHub is here: https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions

GitHub Actions usage is free for both public repositories and self-hosted runners. For private repositories, each GitHub account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account.

I foresee this causing problems in the future. The local build currently doesn't work for me when following the build instructions. I made an issue about the first build error I had here: #20

@simoncozens
Copy link
Contributor

So, if you want actions on private repos, you have to pay? That... doesn't seem like a problem? I'll try and sort the M1 issue though.

@eliheuer
Copy link
Contributor Author

eliheuer commented Jul 12, 2021

I'm just pointing out that this is a cause of friction in the system. The private repo might belong to a large organization where getting something like this approved would take a long time, or a single designer or small organization with no budget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants