ci tooling change?

[davidjgoss]

See:

• https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
• https://blog.travis-ci.com/oss-announcement

Travis is looking like slightly shaky ground now.

Is it worth giving GitHub Actions a try?

cc @charlierudolph @aslakhellesoy

[aslakhellesoy]

Yes - let’s move to GitHub Actions. We discussed this in the weekly meeting on 10th dec too

[davidjgoss]

Okay, we have a workflow in now that tests with our supported Node versions on Linux and Windows. That covers most of what we were doing with Travis and Appveyor.

The only other thing is coverage. Right now we run with coverage on Node 14 but don't seem to do anything with the result.

[davidjgoss]

I see https://coveralls.io/ used a lot in other open source projects. Would be a nice way to get it visible in the PR.

[davidjgoss]

@charlierudolph how do you feel about adding coveralls?

[charlierudolph]

Coverage is currently sent to coveralls but not reported on PRs. I'm good with adding coveralls and getting visibility for it on PRs

[charlierudolph]

Thanks for doing this @davidjgoss. I just disabled the appveyor project so that should stop triggering builds

[aslakhellesoy]

Thanks a lot for doing this @davidjgoss