> but nobody ever says "If your project/team/environment/etc. look like this, then use this model." Honestly, its because a lot of it comes down to preference

> but nobody ever says "If your project/team/environment/etc. look like this, then use this model." Honestly, its because a lot of it comes down to preference and what value you gain from using version control. It is very much like code style standards -- it doesn't matter what is in the standard so much as your teammates all using the same one. If part of the blocker for your team is that no one is experienced enough with git to have a strong opinion, I'd be happy to brainstorm with you for an hour to learn about your current process and offer a tailored opinion.