There are dozens of CI/CD offerings and many are better designed than Github actions, including Gitlab's CI runners.
I don't see what paying Github would do for AWS or GCP. They both have their own code repos, build pipelines, container registries, and more. Even Azure has its own DevOps product.
>>maniga+(OP)
I use Gitlab's CI runners and I agree. However, I am pretty excited about the direction that Github is going with their actions. Having a directory of user created actions and integrations seems like gold to me and I hope Gitlab starts leaning that way soon.
>>jjeaff+R2
I agree, but GitHub must fix the security nightmare that is waiting to happen with GitHub actions marketplace. Seems like this would be such an easy fix, too.
>>hn_thr+Kh1
Organizations can enforce that their repos use only actions that are within the repo, making the build more secure, controlled and auditable.
>>maniga+(OP)
It's all about the ease of use. Manually setting up CI/CD is _hard_ and requires a team to maintain and support it. Whether through a home-rolled Jenkins deployment or Buildkite.