migrate to GH Actions (#190)

* feat(pipeline): test pipeline setup

* feat(pipeline): add build before running e2e

* feat(pipeline): update e2e test pipeline timeout

* feat(pipeline): update readme

* feat(pipeline): add pull request and workflow dispatch per pr request

* chore: remove travis ci config file

* docs: update contributing guidelines

Co-authored-by: jamesgeorge007 <[email protected]>

.github/workflows/ci.yaml

@@ -0,0 +1,27 @@
+name: CI
+on: 
+  push:
+  pull_request:
+    branches:
+      - master
+      - develop
+  workflow_dispatch:
+jobs:
+  job:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: ['ubuntu-latest', 'macos-latest', 'windows-latest']
+        node: ['12', '13', '14']
+    steps:
+    - uses: actions/checkout@v2
+    - name: Setup node
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node }}
+    - name: Install packages
+      run: npm ci
+    - name: Build binaries
+      run: npm run build
+    - name: Run e2e tests
+      run: npm run test

README.md

@@ -74,9 +74,10 @@ Before contributing a change to this repository, please first discuss the change
 2. Fork and clone our repository.
 3. Make your life-changing changes.
 4. Run `npm run build` which generates a `lib` directory with the transpiled `es5` code.
-5. Fire in `npm link` to test everything works fine.
-6. Commit and push your changes.
-7. Make a detailed pull request.
+5. Type in `npm link` to test everything works fine. (Now you've access to the `mevn` root-command.)
+6. Run tests locally before commiting with `npm test`. (If you're having issues running tests locally, then you can commit and use GitHub actions ci in your own fork. All tests should pass.)
+7. Commit and push your changes.
+8. Make a detailed pull request.
 
 > `npm link` creates a symlink in the global folder making the `mevn` command globally available within your local development environment
 

jest/setupE2eTests.js

@@ -1 +1 @@
-jest.setTimeout(240000);
+jest.setTimeout(350000);