Skip to content

Commit

Permalink
chore(ci): pass expected path to validate-commit-msg
Browse files Browse the repository at this point in the history
We pass the path relative to the .git directory, which is what
`validate-commit-msg` is expecting. A few extra items will also
be traced in case anything breaks in the future.

Fixes #2753
  • Loading branch information
chrahunt committed Jul 10, 2017
1 parent 7feaa5c commit 8c98439
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions scripts/validate-commit-msg.sh
Expand Up @@ -19,14 +19,20 @@ if [ -z "$COMMIT_REV" ]; then
exit 1
fi


# Resolve our file for output
# DEV: We use `.git` to avoid cluttering the working directory
GIT_DIR="$(git rev-parse --git-dir)"
TARGET_FILE="$GIT_DIR/VALIDATE_COMMIT_MSG"
TARGET_FILENAME=VALIDATE_COMMIT_MSG
TARGET_FILE="$GIT_DIR/$TARGET_FILENAME"

echo "Retrieving relevant commit message for $COMMIT_REV"
# Output our log message to a file
# DEV: We use `--no-merges` to skip merge commits introduced by GitHub
git log --no-merges --format=format:"%s" -n 1 "$COMMIT_REV" > "$TARGET_FILE"

echo "Validating contents of $TARGET_FILE"
cat "$TARGET_FILE"

# Validate our message
./node_modules/.bin/validate-commit-msg "$TARGET_FILE"
./node_modules/.bin/validate-commit-msg "$TARGET_FILENAME"

0 comments on commit 8c98439

Please sign in to comment.