I am working towards git adoption on a project. One of the concerns is the fear that git history is not guaranteed to be time safe. How can I configure a git repository so users cannot push or pull changes into it that change it's history? This includes keeping users who work directly in the repository from doing a rebase.
I've found...
http://stackoverflow.com/questions/2085871/strategy-for-preventing-or-catching-git-history-rewrite
Which recommends setting...
git config --system receive.denyNonFastforwards true
git config --system receive.denyDeletes true
...Is this enough to guarantee time safe history?
Notes:
1. Only certain process-central repositories would need time safe history.
2. Developers can change their history provided it does not impact anyone else. I don't care about this case (yet).
Brian P. Jones
Senior Software Engineer
Configuration Management