GH Actions

[konsumer]

Related to #88

This adds 2 actions for publishing to Github Pages (I think that needs some config in Settings) and Testing directly in Github Actions.

This improves speed and issue-visibility.

You can see example job-runs:

• pages
• test

And since I have konsumer.js.org hooked up to my github pages, it creates this

It also drops CircleCI, since that is not really needed (Github Actions would take over that job.)

[konsumer]

I think static could depend on test, which would merge the 2 npm ci calls, and not allow a site-publish with failing tests, but it runs pretty fast (even with duplicate installs) so I kept them seperate to make it more clear what each job is doing.

Currently, I didn't have any coverage-gating, but that could be added as part of test job. Coverage, as it is, might be a bit tricky, because we'd need to grab previous coverage, and compare it on test, but I find these kinds of automated tests a bit annoying (often the coverage is not less than it was, just same amount of non-100%, as was the case with my other PR) especially on frontend projects (with limited react-level testing) so I think it's fine without it, personally, but I am willing to look into it, if you are interested in that. I think this can do similar coverage-comparison, but I could also add back circleci (without netlify) and achieve something similar, I think.

[konsumer]

I think I may have added back all the coverage stuff without circleci, in last commit. It seems to hang on curl https://codecov.io/bash but that might be because I haven't set it up for my fork.

It shows nicely in the action-run, though:

[konsumer]

I added a github secret for CODECOV_TOKEN and now it shows up:

So, I think that is all that is needed.

[konsumer]

I'd also like to get rid of these warnings, but it might just be a problem with semantic-ui-react. Have you ever used daisyui? It's a similar UI toolkit, but uses tailwind and produces smaller output (much less CSS and no JS) and has some really nice theming options. I use this a lot for my own projects.

[pawitp]

Hi. While I appreciate the contribution, I'm not looking to migrate any CI/hosting pipeline at the moment. Particularly, what exists right now works fine and the netlify domain performs decently well on SEO.

Netlify also provides a subdomain for every PR.