Too lazy to type, see below 
In theory this should work on big matrix jobs > 256 with splitting, but I haven’t tested that code path yet, maybe we should try building all nixpkgs with this (jk) 
Inspired by GitHub - Defelo/nixpkgs-review-gha: Run nixpkgs-review in GitHub Actions · GitHub and GitHub - garnix-io/garnix-ci: CI and hosting for nix-based, flakified github repos · GitHub (rip)
My hero 
, so much for the value I had in the free tier for garnix.io…
the easiest way to get some of garnix’s feature back is to try atelier and use the free 5g cache allowance from cachix (tho will have to clean out some paths pretty frequently)
or host niks3/attic with r2 or b2 (quite cheap but not free) S3 Provider Comparison · Mic92/niks3 Wiki · GitHub
the garnix.yaml to atelier.toml migration is also really simple unless you are heavily using garnix actions or servers which atelier doesn’t have
Yeah, that’s exactly what I was planning on doing, niks3! Thanks for the tip.
Because GHA is dog slow and has terrible uptime 
Cool tool though, nifty use of GHA!
Because GHA is dog slow and has terrible uptime
not really defending gh but, what’s the comparison? a big self hosted builder ($$$)? and i know everyone is complaining about the uptime, but im not really affected by it
TBH being free for public repos is really the main advantage of GHA, but that IS a pretty big advantage. If you’re willing to spend more time/money on self-hosted or better paid cloud-hosted ones, some of those are better, but “free” is a big advantage.
Some people (many companies, the one I work for included) pay for GHA though, and the uptime and general issues are just not acceptable there.
Our fault for paying GH, of course, and we should just move to another host, but that’s the old tale of lacking standardization and vendor lock-in.
Some people (many companies, the one I work for included) pay for GHA though, and the uptime and general issues are just not acceptable there.
for paying customers, 100%. for people that just want free compute? 
take a look at my usage for the first 3 days of june
but that’s the old tale of lacking standardization and vendor lock-in.
exactly this
