[de_keyboard]

I agree. GitHub Actions should call your scripts but your scripts should not depend on GitHub Actions API.

I also suggest Bazel as a consideration alongside Make. With Bazel, you get two advantages over Make:

1. It is easier to ensure that what GitHub Actions runs and builds is the same as what you have locally, since Bazel can fetch toolchains as part of the build process

2. Using a Bazel remote cache, you do not have to repeat work if the build fails halfway and you need to make some changes before running it again.

[toastal]

Same can be said about Nix and as a bonus you get Nix instead of Starlark

[intelVISA]

Nix & Make is the True Engineer(tm)'s Bazel.

[de_keyboard]

Are Nix and Bazel mutually exclusive?

https://www.tweag.io/blog/2018-03-15-bazel-nix/