> Building it that way is a choice. It's not mandatory. This ^ . In GitHub Actions, I personally try to use pre-baked actions as little as possible, for exactl

> Building it that way is a choice. It's not mandatory. This ^ . In GitHub Actions, I personally try to use pre-baked actions as little as possible, for exactly the reasons I outlined. I prefer GitLab CI, but you can make a mess of that just as easily. In general, if you approach CI as I suggested, you end up with something maintainable regardless of the CI engine in use.