Commit Often, Perfect Later, Publish Once: Git Best Practices

The official and authoritative source for this document has moved. Please update your bookmarks.

You can still use the comments at the bottom of the page to register comments even for the new official location.

You might want to mention bup in the "don't use git as a generic filesystem backup" section. Bup uses the Git repository format with enhancements which give it the ability to handle backups.

In message , Brandon Smith writes:

You might want to mention [bup](http://github.com/apenwarr/bup) in
the "don't use git as a generic filesystem backup" section.  Bup
uses the Git repository format with enhancements which give it the
ability to handle backups.

Done.

                -Seth Robertson

Great article. The format is a little sporadic though. It feels like it should be totally divided into two main parts: "DOs" and "DON'Ts", with "miscellaneous" sections at the end of each. This way "Don't Panic" would fall under the "DON'Ts" section. Then I would also assign verbs as names of each sub-section, for example "Back up" instead of "Backups". This will hopefully help clear up confusing titles like "Sausage Making" since it was hard for me to tell if it was a DO or a DON'T without re-reading it and actually the post-production movie analogy in that section made more sense to me.

Thanks for the comment and suggestions. I see what you mean about the
mixture of dos and don'ts with the dos not specifically marked leading
to potential confusion, I'll probably at least add clarity there.

I am tempted by the segregation idea but either the most important dos
or the most important don't will be deprioritized and I may lose the
lazy reader before they get to the important bits in the other
section.

If you don't understand why someone would hide the sausage making, I
suggest getting a tour of a commercial sausage making facility (if you
can find one which offers such) and find out why they normally hid
such.