Add script to change git settings and use hooks

 - pre-commit hook to check for white-space errors
 - commit-msg hook to ensure commit messages are properly formatted
 - setup line endings and white space
 - pre-push hook to ensure work in progress (AKA WIP) commits are
   not pushed to remote repos

Author: zbeekman

.gitattributes

@@ -9,6 +9,10 @@
 *.F90 text
 *.md text
 *.txt text
+*.sh text
+install_prerequisites/build text
+*.cu text
+*.x64 text
 
 # Denote all files that are truly binary and should not be modified.
 *.mod binary
@@ -22,3 +26,4 @@
 .travis.yml export-ignore
 .gitattributes export-ignore
 .gitignore export-ignore
+developer-scripts export-ignore

developer-scripts/git-hooks/applypatch-msg.sample

@@ -0,0 +1,15 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message taken by
+# applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.  The hook is
+# allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "applypatch-msg".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/commit-msg" &&
+	exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"}
+:

developer-scripts/git-hooks/commit-msg

@@ -0,0 +1,111 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message.
+# Called by "git commit" with one argument, the name of the file
+# that has the commit message.  The hook should exit with non-zero
+# status after issuing an appropriate message if it wants to stop the
+# commit.  The hook is allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "commit-msg".
+
+# Uncomment the below to add a Signed-off-by line to the message.
+# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
+# hook is more suited to it.
+#
+# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
+
+# error message function for writing good commit messages
+error_message () {
+    cat <<\EOF >&2
+Error: bad commit message format. A copy of your commit message is in:
+`.git/COMMIT_EDITMSG`. Please fix it or write a new one according to the
+guidlines below.
+
+The first line of a commit message should start with a capitalized imperative
+verb used in a phrase to summarize the change. This first line must be less
+than 50 characters, followed by an additional blank line. Further detials are
+added after these first two lines, and may be up to 72 characters in length.
+
+This is so that `--oneline` formatted `git log`s will contain human readable,
+meaningful information, and the summaries on Github.com will also contain
+this concise summary. The 72 line limit is to ensure propper formatting on
+all terminals.
+
+Here is an example of a good commit message:
+
+```
+Redirect user to the requested page after login
+
+https://github.com/sourceryinstitute/opencoarrays/Issues/29
+
+Users were being redirected to the home page after login, which is less
+useful than redirecting to the page they had originally requested before
+being redirected to the login form.
+
+* Store requested path in a session variable
+* Redirect to the stored location after successfully logging in the user
+* Fixes #1
+```
+
+As opposed to doing something bad like this:
+
+`git commit -m "Fix login bug"`
+
+For more information on writting good commit messages,
+and keeping a clean history, please see:
+
+ 1. https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
+ 2. http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+ 3. https://www.reviewboard.org/docs/codebase/dev/git/clean-commits/
+
+And for funny examples of what not to do, see: http://whatthecommit.com
+EOF
+
+}
+
+let status=0
+
+# This example catches duplicate Signed-off-by lines.
+
+test "" = "$(grep '^Signed-off-by: ' "$1" |
+	 sort | uniq -c | sed -e '/^[ 	]*1[ 	]/d')" || {
+	echo >&2 "Duplicate Signed-off-by lines."
+	let status=1
+}
+
+# Check that the first line of the commit starts with a
+# capitalized letter.
+if ! (head -n 1 $1 | grep '^[A-Z]' &>/dev/null ); then
+    echo >&2 "First word of commit message must be a capitalized imperative verb.\n"
+    let status=1
+fi
+
+# Check each line for propper length
+ln=0
+cat $1 | \
+    while read line; do
+	let ln+=1
+	nchars=$(wc -c <<<$line)
+	if [[ "$ln" -eq "1" ]]; then
+	    if [[ "$nchars" -gt "51" ]]; then
+		echo >&2 "First line of commit message too long ($nchars > 50 chars)\n"
+		let status=1
+	    fi
+	elif [[ "$ln" -eq "2" ]]; then
+	    if [[ "$nchars" -gt "1" ]] && ! grep '^#' <<<"$line" >/dev/null; then
+		echo >&2 "Second line of commit message not blank\n"
+		let status=1
+	    fi
+	else
+	    if [[ "$nchars" -gt "72" ]]; then
+		echo >&2 "Line $ln of commit message too long ($nchars > 72 chars)\n"
+		let status=1
+	    fi
+	fi
+    done
+
+if [[ $status != 0 ]]; then
+    error_message
+    exit 1
+fi

developer-scripts/git-hooks/post-update.sample

@@ -0,0 +1,8 @@
+#!/bin/sh
+#
+# An example hook script to prepare a packed repository for use over
+# dumb transports.
+#
+# To enable this hook, rename this file to "post-update".
+
+exec git update-server-info

developer-scripts/git-hooks/pre-applypatch.sample

@@ -0,0 +1,14 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed
+# by applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-applypatch".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/pre-commit" &&
+	exec "$GIT_DIR/hooks/pre-commit" ${1+"$@"}
+:

developer-scripts/git-hooks/pre-commit

@@ -0,0 +1,85 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed.
+# Called by "git commit" with no arguments.  The hook should
+# exit with non-zero status after issuing an appropriate message if
+# it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-commit".
+
+function ends_with_newline() {
+    test ! -s "$1" || test $(tail -r -c1 "$1" | xxd -ps) = "0a"
+}
+
+function ends_with_single_new_line () {
+    tail -2 "$1" | ( read x && read y && ! grep '^[[:blank:]]\+$' <<<$x >/dev/null)
+}
+
+if git rev-parse --verify HEAD >/dev/null 2>&1
+then
+	against=HEAD
+else
+	# Initial commit: diff against an empty tree object
+	against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
+fi
+
+# if we are in the middle of merging skip hooks
+MERGING=$(git rev-parse MERGE_HEAD 2>&1)
+if [[ $? == 0 ]]; then
+  exit 0
+fi
+
+# if we are in the middle of merging skip hooks
+PICKING=$(git rev-parse CHERRY_PICK_HEAD 2>&1)
+if [[ $? == 0 ]]; then
+  exit 0
+fi
+
+# If you want to allow non-ASCII filenames set this variable to true.
+allownonascii=$(git config --bool hooks.allownonascii)
+
+# Redirect output to stderr.
+exec 1>&2
+
+let status=0
+# Cross platform projects tend to avoid non-ASCII filenames; prevent
+# them from being added to the repository. We exploit the fact that the
+# printable range starts at the space character and ends with tilde.
+if [ "$allownonascii" != "true" ] &&
+	# Note that the use of brackets around a tr range is ok here, (it's
+	# even required, for portability to Solaris 10's /usr/bin/tr), since
+	# the square bracket bytes happen to fall in the designated range.
+	test $(git diff --cached --name-only --diff-filter=A -z $against |
+	  LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
+then
+	cat &>2 <<\EOF
+Error: Attempt to add a non-ASCII file name.
+
+This can cause problems if you want to work with people on other platforms.
+
+To be portable it is advisable to rename the file.
+
+If you know what you are doing you can disable this check using:
+
+  git config hooks.allownonascii true
+EOF
+	let status=1
+fi
+
+# If there is a file that does not end with a newline, print its name and fail.
+for f in $(git diff-index --name-status --cached $against | grep -v ^D | cut -c3-); do
+    if [[ "$f" =~ ([.](h|m|c|rb|sh|py|txt|md|f90|F90|cmake|x64|csh)|makefile|Makefile)$ ]] ||
+       head -n 1 | grep '^#!/'; then
+	if ! ends_with_newline "$f"; then
+	    echo &>2 "No newline at end of file: $f\n"
+	    let status=1
+	fi
+    fi
+done
+
+# If there are whitespace errors, print the offending file names and fail.
+git diff-index --check --cached $against -- || let status=1
+
+if [[ $status != 0 ]]; then
+    exit 1
+fi

developer-scripts/git-hooks/pre-push

@@ -0,0 +1,52 @@
+#!/bin/bash
+
+# An example hook script to verify what is about to be pushed.  Called by "git
+# push" after it has checked the remote status, but before anything has been
+# pushed.  If this script exits with a non-zero status nothing will be pushed.
+#
+# This hook is called with the following parameters:
+#
+# $1 -- Name of the remote to which the push is being done
+# $2 -- URL to which the push is being done
+#
+# If pushing without using a named remote those arguments will be equal.
+#
+# Information about the commits which are being pushed is supplied as lines to
+# the standard input in the form:
+#
+#   <local ref> <local sha1> <remote ref> <remote sha1>
+#
+# This sample shows how to prevent push of commits where the log message starts
+# with "WIP" (work in progress).
+
+remote="$1"
+url="$2"
+
+z40=0000000000000000000000000000000000000000
+
+while read local_ref local_sha remote_ref remote_sha
+do
+	if [ "$local_sha" = $z40 ]
+	then
+		# Handle delete
+		:
+	else
+		if [ "$remote_sha" = $z40 ]
+		then
+			# New branch, examine all commits
+			range="$local_sha"
+		else
+			# Update to existing branch, examine new commits
+			range="$remote_sha..$local_sha"
+		fi
+
+		# Check for WIP commit
+		commit=`git rev-list -n 1 --grep '^WIP' "$range"`
+		if [ -n "$commit" ]
+		then
+			echo >&2 "Found WIP commit in $local_ref, not pushing"
+			exit 1
+		fi
+	fi
+done
+exit 0