Github actions CI

[pedrofurtado]

@prodis 👍

the output of CI can be checked here (until PR merged): https://github.com/pedrofurtado/correios-cep/actions/runs/1095889282

[prodis]

@pedrofurtado Thank you for your PR. But what is the motivation to move the CI from Travis to GitHub Actions?

[pedrofurtado]

Hi, @prodis ! The motivation and suggestion is because Github Actions have a great ecosystem of actions/plugins/and so on, better native integration with github repos (it's made by github itself, has "actions" tab in repo and so on) and a growing popularity and adoption, especially in open source projects. It's also free and works out-of-box very well 👍 🍻

[prodis]

I see that GitHub Actions is trending, but you didn't mentioned any real advantage comparing to the current CI in Travis. In fact, the GitHub Actions configuration you proposed is missing the allowed failure Ruby versions and the cron jobs.