Your CI should be disposableYour CI should be disposable<br>Your CI should have one job: scheduling. It should decide<br>when to do the thing. Your builds itself, should be<br>controlled by you. Use Docker, Nix, a Makefile or what have<br>you. The ideal workflow file looks like this:

steps:<br>name: Do the thing<br>run: nix build .#

This way, you can always run your CI locally, its just one<br>command after all.

Don't use CI as a way to install packages, compilers, shared<br>libraries, toolchains. Do use it to schedule builds.

The next time GitHub Actions goes down, you'll still be able<br>to deliver your software. Consider an<br>alternative though.