Update TravisCI to use exiting env var
$TRAVIS_COMMIT_RANGE was broken but it seems what we're doing is worse and resulting in false negatives. The result of the bad range was that we weren't running lint or tests for things we should have been. It actually looks like $TRAVIS_COMMIT has been wrong and it's not clear why this has been working at all.
Paul O’Shannessy committed
Mar 13, 2015 at 18:34 UTC
08b1515f7fb82c64b3f218bf60964b6b75fa6be6
1 file changed
-4
.travis.yml
-4
@@ -8,10 +8,6 @@ cache:
8
- node_modules
9
before_install:
10
- |
11
- if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then
12
- PR_FIRST=$(curl -s https://github.com/${TRAVIS_REPO_SLUG}/pull/${TRAVIS_PULL_REQUEST}.patch | head -1 | grep -o -E '\b[0-9a-f]{40}\b' | tr -d '\n')
13
- TRAVIS_COMMIT_RANGE=$PR_FIRST^..$TRAVIS_COMMIT
14
- fi
11
git diff --name-only $TRAVIS_COMMIT_RANGE | grep -qvE '(\.md$)|(^(docs|examples))/' || {
12
echo "Only docs were updated, stopping build process."
13
exit