text
stringlengths 0
9.36M
|
|---|
# 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 <<\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
|
exit 1
|
fi
|
# If there are whitespace errors, print the offending file names and fail.
|
exec git diff-index --check --cached $against --
|
File: .git/hooks/post-update.sample
|
Contents:
|
#!/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
|
File: .git/hooks/commit-msg.sample
|
Contents:
|
#!/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"
|
# 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.
|
exit 1
|
}
|
File: .git/hooks/pre-rebase.sample
|
Contents:
|
#!/bin/sh
|
#
|
# Copyright (c) 2006, 2008 Junio C Hamano
|
#
|
# The "pre-rebase" hook is run just before "git rebase" starts doing
|
# its job, and can prevent the command from running by exiting with
|
# non-zero status.
|
#
|
# The hook is called with the following parameters:
|
#
|
# $1 -- the upstream the series was forked from.
|
# $2 -- the branch being rebased (or empty when rebasing the current branch).
|
#
|
# This sample shows how to prevent topic branches that are already
|
# merged to 'next' branch from getting rebased, because allowing it
|
# would result in rebasing already published history.
|
publish=next
|
basebranch="$1"
|
if test "$#" = 2
|
then
|
topic="refs/heads/$2"
|
else
|
topic=`git symbolic-ref HEAD` ||
|
exit 0 ;# we do not interrupt rebasing detached HEAD
|
fi
|
case "$topic" in
|
refs/heads/??/*)
|
;;
|
*)
|
exit 0 ;# we do not interrupt others.
|
;;
|
esac
|
# Now we are dealing with a topic branch being rebased
|
# on top of master. Is it OK to rebase it?
|
# Does the topic really exist?
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.