The team I'm on at work will be transitioning to Git within the next week or two. This quote is very relevant to what I expect we'll go through.

"How does this work?" or sometimes "Ugh! This commit history is a mess!" This is a shorthand for people using Git inconsistently because of a lack of documentation. Managers and teams need to insist on having up-to-date, readily available documentation on how the workflow works (including copy-paste-able Git commands). We don't do nearly enough to support our future selves, and onboard new hires. By having that documentation, you can ensure there's exactly one way that the team uses Git. Consistency is really important if you want to have predictable information when you're using advanced debugging techniques. (Un)fortunately Git core won't help you to enforce that consistency.

I've created a few documents on our Confluence, including a few video walkthroughs, but there's some resistance to creating and consuming documentation within the team. Not sure how to get everyone to spend sometime getting to understand Git before jumping in. The words "I just want to know enough to get through the day" have been uttered in our standups. I fear that if that becomes the general practice of the devs, we'll get into some sticky situations where git will be blamed due to lack of knowledge.

Has anyone else gone through such a switch? Btw, we're coming from a Microsoft environment where we use TFS and Visual Studio heavily. We'll be using a mix of SourceTree and Visual Studio Git integrations for most of the work.