Neal Kreitzinger <nkreitzinger@xxxxxxxxx> writes: > hooks/post-update is: > > git stash save > echo "worktree+index of non-bare remote current branch stashed for safety" > git reset --hard > echo "git-reset --hard on current remote branch to ensure clean state" > > message is echoed, but git-reset --hard does not appear to have really > worked. (git 1.7.1) Have you checked where in the filesystem hierarchy that script is run (hint: pwd)? Also it is unclear why you keep saying "stash". What kind of changes are you expecting to be saved to the stash? Will they be changes that are not source controlled that you would rather not to see? In other words, after running "stash" every time somebody pushes and having accumulated many stash entries, when do you plan to pop these stashed changes? I would have expect that such a repository to reject a push if the working tree is dirty, and run checkout in post-update, though. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html