Building a Github-specific CI pipeline similarly transfer it into a set of executable steps. The only difference is that you are now tied to a vendor for execu

Building a Github-specific CI pipeline similarly transfer it into a set of executable steps. The only difference is that you are now tied to a vendor for executing that logic, and the issue is really that this tooling is proprietary software (otherwise, you could just take their theoretical open source runner system and run it locally). To me, this is mostly a question of using non-open-source development tools or not.