From bca2d01e18e69ae7b602950ee640a08ea1c8cef0 Mon Sep 17 00:00:00 2001 From: Caleb Maclennan Date: Sat, 19 Oct 2013 19:35:10 -0600 Subject: [PATCH] add sample hooks that allow cloning over extant files Cloning a repo over an existing set of files would usually cause a merge conflict that aborts the process and requires manual intervention. This pair of hooks handles that case by manually moving the extant objects out of the way, completing the checktout, then restoring them to their original places. The resulting state is a set of unstaged local changes. --- doc/hooks | 4 ++-- doc/sample_hooks/post-merge-unclobber | 10 ++++++++++ doc/sample_hooks/pre-merge-unclobber | 11 +++++++++++ 3 files changed, 23 insertions(+), 2 deletions(-) create mode 100755 doc/sample_hooks/post-merge-unclobber create mode 100755 doc/sample_hooks/pre-merge-unclobber diff --git a/doc/hooks b/doc/hooks index 30cd373..282ee86 100644 --- a/doc/hooks +++ b/doc/hooks @@ -15,11 +15,11 @@ Available hooks are: * pre-init * post-init * pre-merge - Use this hook to detect and handle merge conflicts before vcsh's native code + Use this hook to detect and handle merge conflicts before vcsh's native code finds and errors on them. This is useful for allowing clones on top of existing files. * post-merge - Use this hook to finish handling any merge conflicts found in the pre-merge hook. + Use this hook to finish handling any merge conflicts found in the pre-merge hook. * pre-pull * post-pull * pre-push diff --git a/doc/sample_hooks/post-merge-unclobber b/doc/sample_hooks/post-merge-unclobber new file mode 100755 index 0000000..017a13f --- /dev/null +++ b/doc/sample_hooks/post-merge-unclobber @@ -0,0 +1,10 @@ +#!/bin/sh + +# This finds objects that the pre-merge script moved out of the way to +# avoid conflicts when running git clone and moves them back to their +# original places. The result is that the git repository gets checked out +# and the extant objects end up back in the working directory. Git now +# sees these as un-staged changes to the working branch and you can deal +# with them by adding them or reverting. + +find -name '*.vcsh-unclobber' -execdir rename .vcsh-unclobber '' {} \; diff --git a/doc/sample_hooks/pre-merge-unclobber b/doc/sample_hooks/pre-merge-unclobber new file mode 100755 index 0000000..93a7319 --- /dev/null +++ b/doc/sample_hooks/pre-merge-unclobber @@ -0,0 +1,11 @@ +#!/bin/sh + +# This code does amost exactly what the native VCSH sanity checking code +# does except that on finding a potential merge conflict, it moves the +# extant object out of the way temporarily. The merge then happens cleanly +# as far as git knows, and a post-merge hook can figure out what to do with +# the extant versions of the objects. + +for object in $(git ls-tree -r origin/master | awk '{print $4}'); do + [ -e "$object" ] && mv "$object" "$object.vcsh-unclobber" +done -- 2.39.2