Migrate from Travis-CI to Github Actions

[yamalight]

Initial work for server has been done in https://github.com/exoframejs/exoframe-server/pull/33 (huge thanks to @anbraten).

Things to do:

• [x] Replace badges in readme
• [x] Add coveralls to all server tests
• [x] Auto-bump fix version in npm before publishing from develop
• [x] Migrate CLI to github actions

[anbraten]

Github actions seems to work quite well with a monorepo:

on:
  push:
    branch: develop
    paths:
      - 'packages/cli/**'

As the issues and documentation are already inside this main repo, I think adding the server and maybe later the other packages sounds quite handy to me.

[yamalight]

@anbraten wouldn't those actions run on every commit though? Or does github handles executions in "smart" way only when something's changed? 🤔

[anbraten]

on -> paths is a quite nifty feature by github. It checks if a push has changed a file inside its defined path-pattern. Docs

We could simply write separate workflows for the cli, server packages.

[yamalight]

@anbraten oooh, that's pretty awesome! thanks for bringing that to my attention. that makes mono-repo quite compelling actually 🤔

[yamalight]

This needs to happen faster because after latest update Travis started randomly breaking builds for no apparent reason, which is pretty infuriating to fix 🤦‍♂️ Gotta find few hours to address this..

[FDiskas]

Please update issue what else should be done. Looks like pull request https://github.com/exoframejs/exoframe-server/pull/37 was merged and coverage is fixed already

[yamalight]

@FDiskas just two small tasks left - change readme badges & add coveralls to all exoframe-server test executions (currently only runs on release)

[FDiskas]

This ticket should go to server repo?

[yamalight]

@FDiskas server repo doesn't have issues, all of them are tracked here

[yamalight]

This is now done.