Skip to content

Instantly share code, notes, and snippets.

@clijiac
Created March 20, 2019 01:28
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save clijiac/a1a54c63e560b93d1374578fbedc0877 to your computer and use it in GitHub Desktop.
Save clijiac/a1a54c63e560b93d1374578fbedc0877 to your computer and use it in GitHub Desktop.
prepare-commit-msg
#!/bin/sh
#
# An example hook script to prepare the commit log message.
# Called by "git commit" with the name of the file that has the
# commit message, followed by the description of the commit
# message's source. The hook's purpose is to edit the commit
# message file. If the hook fails with a non-zero status,
# the commit is aborted.
#
# To enable this hook, rename this file to "prepare-commit-msg".
# This hook includes three examples. The first comments out the
# "Conflicts:" part of a merge commit.
#
# The second includes the output of "git diff --name-status -r"
# into the message, just before the "git status" output. It is
# commented because it doesn't cope with --amend or with squashed
# commits.
#
# The third example adds a Signed-off-by line to the message, that can
# still be edited. This is rarely a good idea.
#SOB=`git rev-parse --abbrev-ref HEAD | sed -e '/jia\//g'`
#grep -qs "^$SOB" "$1" || echo "[$SOB]" >> "$1"
# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
#BRANCH=`git rev-parse --abbrev-ref HEAD | sed -n 's/jia/#' `
#echo "[$BRANCH]" > "$1.msg"
#cat "$1" >> "$1.msg"
#cat "$1.msg" > "$1"
#NAME=$(git branch | grep '*' | sed 's/* //')
NAME=$(git rev-parse --abbrev-ref HEAD|sed 's/jia\/\(.*\)/\1/gm')
#DESCRIPTION=$(git config branch."$NAME".description)
if [ -n "$NAME" ] && [ "$NAME" != "smartgit-temp" ]; then
sed -i.bak -e "1s/^/[$NAME]: /" $1
#echo '['"$NAME"]': '$(cat "$1") > "$1"
#echo "[$NAME]: $(cat $1)" > $1
fi
#if [ -n "$DESCRIPTION" ]
#then
# echo "" >> "$1"
# echo $DESCRIPTION >> "$1"
#fi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment