Add GitHub Actions config file

[abetomo]

You can also test on Windows.

Pull Request

Problem

We were not using Windows CI.

Solution

Use GitHub Actions to test on Windows.

ChangeLog

[shadowspawn]

Nice! I will research a bit about Github Actions before reviewing.

(There will likely be some minor code changes to get current tests running and passing on Windows: #916 )

[shadowspawn]

3.0.1 is out, so keen to give this a go! (Did you sign up for the beta?)
I expect the Windows build will break, but that is ok.
Not sure if this will be active from develop branch, but will try that first.

Thanks @abetomo. I was thinking of the Azure PR we got a while ago but I like this better.

[shadowspawn]

Might want to call it tests.yml?

[shadowspawn]

I'll let you do the merge @abetomo. Keen to see what happens. 🙂

[abetomo]

Renamed the configuration file, and fixed the problem with the settings.

This was the result for my repository.
https://github.com/abetomo/commander.js/runs/207808904

This repository is also valid, so it will work if merged.

[abetomo]

https://github.com/tj/commander.js/runs/207817593
It seems that this repository worked when merged with develop.

[shadowspawn]

Nice! How do you see the runs? (When I go to Actions I just see templates, but I can follow your link and see that run.)

[abetomo]

Probably, you can see it from the 'Actions' tab once it has been merged with master.

[shadowspawn]

I have signed up for the Actions beta, I might be able to see more when accepted.

It does not look like the test are running on Windows, but I was not sure why on first look.

(Woop woop! Thanks.)

[abetomo]

It's hard to see in the capture, but it seems to work on Windows.

[shadowspawn]

I got added to the beta program, and can see the past workflow runs now. I am still suspicious whether the Windows test are running but clearly they are meant to. Looking forward to merging with the Jest branch. Exciting!