>I wonder if this might be an educational issue? It certainly is. There are two things that a team needs to do to use git: 1) Team members all learn git 2) A

>I wonder if this might be an educational issue? It certainly is. There are two things that a team needs to do to use git: 1) Team members all learn git 2) A few conventions are agreed upon to facilitate collaboration People use #2 to replace #1. And that's why we've had to sit through a neverending flow of blog posts obsessing over git workflows. Git is flexible to whatever your business workflow is, play around with it a bit, choose something, then make changes when it's not working. The topic fundamentally does not need this many explainers. But if you're supplanting understanding the tool, it does.