Migrate to GitHub Actions

[foolip]

An umbrella issue for migrating from Travis CI to GitHub Actions. Repositories would be affected (current have a .travis.yml file):

Living Standards

• compat
• console
• dom
• encoding
• fetch
• fullscreen
• html
• infra
• mimesniff
• notifications
• quirks
• storage
• streams
• url
• xhr

Others

• books
• figures
• html-build
• html-differences (archived)
• misc-server
• participate.whatwg.org
• platform.html5.org
• sg
• wattsi
• whatwg.org

[annevk]

Given that the secrets would become centralized I think we could also move the configuration file for standards to https://github.com/whatwg/spec-factory.

[foolip]

whatwg/whatwg.org#322 is what's needed for deploy.sh, and whatwg/fullscreen#173 is trying it with Fullscreen.

@annevk a bunch of specs have customized build steps and so will differ somewhat, is that OK or will intentional differences have to be annoying every time factory.py is run?

[annevk]

We could encode intentional differences in factory.json as we have done for other such things. That might be nice to keep the knowledge of such things centralized, but I can also see that as being an argument for not trying to adopt spec-factory for it now.

[foolip]

https://github.com/whatwg/encoding/blob/master/Makefile is an example of this. How is that currently managed?

[annevk]

That's a somewhat special case. The templated bit is @@bs@@ which occurs several times in https://github.com/whatwg/spec-factory/blob/master/Makefile.template. https://github.com/whatwg/spec-factory/blob/master/factory.py#L56 fills in that variable by looking at the filename of the only .bs file in the repository.

(We could replace this with using factory.json if we want I suppose. That didn't exist at first.)

[domenic]

I'm a bit confused by the last few comments. The Makefile in encoding is already generated by spec-factory, using https://github.com/whatwg/spec-factory/blob/202daf74a12c784a58c7184378bd16cf92dc3963/factory.json#L9-L11 .

I think @annevk was suggesting generating the .travis.yml counterpart in spec-factory. The variance there is:

• ENCRYPTION_LABEL is different in each spec
• Some specs require different dependencies, e.g. Encoding requires Python, Streams requires Node.js and does some stuff with the reference implementation.