Makes sense for sure. I think GitHub Actions should be fine for GitCitadel’s own development needs. Plenty of massive OSS projects using it. GitHub’s fair usage policies are pretty reasonable. I’ve hit some GitHub API usage limits in the past, but that was on me for pushing it too far and not properly optimising some heavier workflows.

As for building CI as a service for others on top of GitHub’s infrastructure… that’s a bit trickier. The limits are generous, but not that generous. Plus, I’m not sure if it would violate their usage terms. It might be worth reading up on or even reaching out to them.

https://docs.github.com/en/actions/administering-github-actions/usage-limits-billing-and-administration

https://docs.github.com/en/site-policy/github-terms/github-terms-of-service

https://docs.github.com/en/site-policy/github-terms/github-terms-for-additional-products-and-features#a-actions-usage

From the last link above:

Actions should not be used for:

* The provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes;

* Any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or

* If using GitHub-hosted runners, any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used