Merge pull request #25 from codeshifu/ch/ci

CI with Coverage Reporting

.travis.yml

@@ -11,7 +11,7 @@ notifications:
 script:
   - npm run test
 after_success:
-  - npm run coverage
+  - npm run test:coverage
 branches:
   only: master
   except: /^v\d+\.\d+\.\d+$/

package.json

@@ -5,13 +5,13 @@
   "main": "dist/cli.js",
   "scripts": {
     "clean": "rimraf dist",
-    "bundle": "parcel build cli.ts --target node --no-cache",
+    "bundle": "parcel build cli.ts --target node --no-cache --no-source-maps",
     "build": "npm-run-all --parallel clean bundle",
     "build:start": "npm run build -- start",
     "dev": "nodemon --ext ts,json --exec 'npm run build && node dist/cli.js'",
     "start": "node dist/cli.js",
     "test": "jest",
-    "test:coverage": "jest --coverage",
+    "test:coverage": "jest --coverage --coverageReporters=text-lcov | coveralls",
     "test:watch": "jest --watch"
   },
   "bin": {
@@ -23,11 +23,11 @@
   },
   "keywords": [
     ".env",
-		"slack",
-		"dotenv",
-		"environment variables",
-		"sync env slack",
-		"sync dotenv slack"
+    "slack",
+    "dotenv",
+    "environment variables",
+    "sync env slack",
+    "sync dotenv slack"
   ],
   "files": [
     "readme.md",
@@ -55,6 +55,7 @@
     "@types/ora": "3.2.0",
     "@types/pkg-conf": "3.0.0",
     "@types/temp-write": "4.0.0",
+    "coveralls": "3.0.7",
     "jest": "24.9.0",
     "nodemon": "1.19.3",
     "npm-run-all": "4.1.5",

readme.md

@@ -3,6 +3,8 @@
 
 ![sync-dotenv-slack-demo](https://media.giphy.com/media/Xd744GG44wZWXJzdJb/giphy.gif)
 
+![Travis (.org)](https://img.shields.io/travis/codeshifu/sync-dotenv-slack) [![Coverage Status](https://coveralls.io/repos/github/codeshifu/sync-dotenv-slack/badge.svg?branch=master)](https://coveralls.io/github/codeshifu/sync-dotenv-slack?branch=master)
+
 While having a `.env.example` file committed to source control might help in letting teammates know that certain environmental variables are required to get up and running with a project, getting them the values can be a pain. Even worse, alerting them when any of those values (or variables) changes can be a drag.
 
 `sync-dotenv-slack` automates the process of keeping your teammates in the loop when `.env` changes (locally) by securely notifying them on Slack.