Re: Disallow amending published commits?

[James Pickens <jepicken@gmail.com>]

[Resend since I forgot to cc the list]

On Sat, Mar 21, 2009, Peter Harris <git@peter.is-a-geek.org> wrote:
> 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.

Thanks, but unfortunately that won't work in our workflow.  Users never
push their changes; instead, they do a turnin to a continuous integration
server.  The server clones the central repo, pulls their changes into the
clone, builds and tests it, then pushes to the central repo if it passes
the tests.  So integration happens via 'pull' instead of 'push'.

We can't force the pulls to be fast forward only, because we need to allow
turnins from multiple users to be built and tested in parallel, without
requiring users to pull from each other or otherwise coordinate their
turnins.

James