-
-
Save lyrixx/5867424 to your computer and use it in GitHub Desktop.
#!/bin/bash | |
# Put this file at: .git/hooks/post-checkout | |
# and make it executable | |
# You can install it system wide too, see http://stackoverflow.com/a/2293578/685587 | |
PREV_COMMIT=$1 | |
POST_COMMIT=$2 | |
NOCOLOR='\e[0m' | |
REDCOLOR='\e[37;41m' | |
if [[ -f composer.lock ]]; then | |
DIFF=`git diff --shortstat $PREV_COMMIT..$POST_COMMIT composer.lock` | |
if [[ $DIFF != "" ]]; then | |
echo -e "$REDCOLOR composer.lock has changed. You must run composer install$NOCOLOR" | |
fi | |
fi |
Other solution: commit your dependencies.
@fzaninotto: I usually apply the following rule: I only commit the code that I am maintaining. Committing dependencies sometimes lead to a messy or too big repository, depending on what is inside dependencies.
@skyzyx here is a potential fix:
#!/bin/bash
# Put this file at: .git/hooks/post-checkout
# and make it executable
# You can install it system wide too, see http://stackoverflow.com/a/2293578/685587
PREV_COMMIT=$1
POST_COMMIT=$2
GIT_DIR=$(git rev-parse --git-dir)
GIT_DIR_MERGE="$GIT_DIR"/rebase-merge
GIT_DIR_APPLY="$GIT_DIR"/rebase-apply
GIT_MERGE_REBASE=false
[[ (-d "$GIT_DIR_MERGE" && -f "$GIT_DIR_MERGE/interactive") || -d "$GIT_DIR_APPLY" ]] && GIT_MERGE_REBASE=true
NOCOLOR='\e[0m'
REDCOLOR='\e[37;41m'
function composerlock {
echo -e "$REDCOLOR composer.lock has changed: running composer install $NOCOLOR"
COMPOSER=
if [ -f composer.phar ]; then
COMPOSER="php composer.phar"
fi
which composer > /dev/null 2>&1
if [ $? ]; then
COMPOSER="composer"
fi
if [[ $GIT_MERGE_REBASE = false && -n "$COMPOSER" ]]; then
$COMPOSER install
fi
}
function packagejson {
echo -e "$REDCOLOR package.json has changed: running npm install $NOCOLOR"
which npm > /dev/null 2>&1
if [[ $GIT_MERGE_REBASE = false && $? ]]; then
npm install
fi
}
FUNCS=$(declare -F -p | cut -d " " -f 3)
for FUNC in $FUNCS
do
DIFF=$(git diff --shortstat $PREV_COMMIT..$POST_COMMIT $FUNC 2>/dev/null)
if [[ $DIFF != "" ]]; then
$FUNC
fi
done
wow nice script i was also checking the dump-sql http://www.craftitonline.com/2013/08/symfony2-checks-for-composer-and-database/
@jubianchi -
I'm aware this is old, but there is a bug in your script:
$GIT_MERGE_REBASE
will always be false, as the hook is run before the rebase_apply
dir is created. At least in git 2.9
Quick download of this file from CLI:
curl -Ls https://gist.githubusercontent.com/lyrixx/5867424/raw/0af090ab37d07a4d814c1ee2a267fad90767565d/post-checkout \
> "$(git rev-parse --git-dir)/hooks/post-checkout"
Guys, is there any chance to run it on git pull/merge? In a nutshell, on any update.
Hook files as post-update
, post-receive
don't work.
I made this script for testing and it didn't show any red message.
git checkout 1.1.0
git branch -d master
git checkout 1.1.0 -b master
git branch --set-upstream-to=origin/master master
git pull
@andkirby don't forget to chmod +x
curl -Ls https://gist.githubusercontent.com/lyrixx/5867424/raw/0af090ab37d07a4d814c1ee2a267fad90767565d/post-checkout \
> "$(git rev-parse --git-dir)/hooks/post-checkout" && chmod +x "$(git rev-parse --git-dir)/hooks/post-checkout"
Using the version by @jubianchi on OS X I get