Does there exist Git commit policies? E.g. when and what to commit?

Question

Hi,

We are going to use Git where I work, and we have some in house programmers, and some external freelance programmers that have never used Source Control Management before.

The reason we want to use Git is to be better at communicating with the freelance programmers, and to avoid code from being lost and in general track what they do.

So now we need a commit policy. I.e when should users commit, and when should they rebase commits and so on.

Does there exist written policies from other projects that I can read?

Or does someone know of good practices that we should use?

Answer 1

Git is designed to be as flexible as possible in this regard. However, there are some common deployment models. A good overview can be found in the ProGit Workflow section.