Consider migrating from Travis CI to GitHub Actions

[asahasrabuddhe]

Issue Description

As of today, echo uses Travis CI for testing. I propose that we move from Travis CI and use GitHub Actions. If we go through with this change, we would be able to test out echo on Windows, Mac, and Linux very easily. It would also allow us to automate the release process also.

Please let me know your thoughts on this.

[lammel]

Travis CI seems to be causing a some issues with failed builds lately for quite some projects I watch.

As long as automatic testing of PRs works and it's integrated into github it's fine.
Automating releases might help when more maintainers are doing releases.

I never looked into github actions though, but from what I see you still need some tool to actually run the test (e.g. the circle CI action). Any details on what you are planning here?

[asahasrabuddhe]

Here’s the thing

GitHub actions is independent of any other CI system and the virtual machines that execute the tests are provided by GitHub to us.

On our part, we have to create a yml file to configure the build steps etc.

I have already implemented GitHub actions on some other repos I help maintain and we have the following configuration in place. For any PR to the master branch we run the test suite and when any tags are pushed to master we make a release.

Let me work on a PR so you get a better insight about what I’m talking about.

[lammel]

@asahasrabuddhe Sounds great then, looking forward to the PR