What's the difference between this and Travis ci ?
Great question! I'm not familiar with all the ins and outs of Travis CI, but you can accomplish much of the same thing with both -- automating your software development lifecycle from build, test, package, release, publish, to deployment. One of the arguments for GitHub Actions vs something like a Travis CI or Circle CI is having the automated process defined and versioned right alongside your code.
It was the very first question in my head during reading about Actions.
Even more, I'm pretty sure that under the hood Github Actions uses at least some of Travi's infrastructure/components.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.