Replace Travis CI with GitHub actions

[shakeelmohamed]

Travis CI and Codeclimate have been broken for months.
I'm not sure what's wrong, let's give actions a try

Zombie tests are hanging, probably a good time to switch to puppeteer now https://github.com/puppeteer/puppeteer

[Dragonashes]

The yellow warnings related to CSS cant cause it, it runs tasks which is confusing but also good. It hangs and based on time running i would think the red error is a timeout.

The yellow warning
Warning: 83:9 warning Unexpected console statement no-console
Warning: 260:13 warning Unexpected console statement no-console
Warning: 325:5 warning Unexpected console statement no-console

is likely the cause

I am not sure what uses no-console but the .yml says ESLINT, it says here https://eslint.org/docs/rules/no-console that it is used for debugging; I dont know if that is what prints messages to github but perhaps it is supposed to be off on Githubs virtual machines? which could possibly mean, if the (.codeclimate.yml ?) file syntax is right that

no-console:
        enabled: true

might fix it or removing the line if that works.

only other thing i can think of is .travis.yml has a node.js 8/10 version but 14.18.1 is latest, node.js github might have complications if not latest ?

I dont have too much knowledge on this stuff.

[shakeelmohamed]

@Dragonashes yeah there's some issue with ZombieJS the headless browser we use for tests (which is no longer maintained). The tests only started hanging in newer versions of node.js.

The ideal solution is to swap out Zombie for Puppeteer instead.

You can ignore those warnings from eslint, they are unrelated to the tests hanging

[Dragonashes]

I have taken several looks and concluded i would need someone else involved albeit more than a writeup. I could end up getting in the way if someone else takes it but i will gladly help.