Travis checks the environment for unexpected changes before passing

leebyron · leebyron · commit 0c12cea7376a · 2017-03-08T20:17:36.000-08:00
diff --git a/.travis.yml b/.travis.yml
@@ -3,6 +3,7 @@ language: node_js
 node_js: 7
 
 cache: yarn
+script: npm run test:travis
 
 env:
   global:
diff --git a/package.json b/package.json
@@ -31,6 +31,7 @@
     "format": "prettier --single-quote --write \"{src,pages/src,pages/lib}/**/*.js\"",
     "testonly": "./resources/jest",
     "test": "run-s format build lint testonly type-check",
+    "test:travis": "npm run test && ./resources/check-changes",
     "type-check": "cd type-definitions/tests && flow check",
     "perf": "node ./resources/bench.js",
     "start": "gulp --gulpfile gulpfile.js dev",
diff --git a/resources/check-changes b/resources/check-changes
@@ -0,0 +1,13 @@
+#!/bin/bash -e
+
+if ! git diff --quiet; then echo "
+
+$(tput setf 4)The Travis build resulted in additional changed files.
+Typically this is due to not running $(tput smul)npm test$(tput rmul) locally before
+submitting a pull request.
+
+The following changes were found:$(tput sgr0)
+";
+
+  git diff --exit-code;
+fi;
