On Sat, Mar 21, 2009 at 1:56 PM, James Pickens wrote: > I wanted to have a pre-commit hook that would prevent users from > amending a commit that had already been published, but I couldn't > find any way in the pre-commit hook to figure out if --amend was > used. Is there a way to do that? Or any better way to disallow > amending published commits? An amended commit will have a new SHA1, and therefore git will treat it as an entirely different commit. Trying to push an amended history is 'non fast forward' in git terminology, since it involves a rewind of existing history. Set receive.denyNonFastForwards if you don't want people to be able to amend (or otherwise rewind) published history. Peter Harris -- 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
