Probably this is not the best git article on the web, and neither should it be. I won't be covering a lot of parts considered essential of git and explaining how things work under the hood. This tends to be a much more practical guide, assuming zero knowledge and enough for working on a team

• what is git and why should you use it
• how is that different from GitHub
• the basics: start tracking your progress with commits
• the pitfalls of using a single branch and why gitflow
• working with branches and creating pull requests
• dealing with conflicts
• the extra mile: differences between merge x rebase, squash commits, git-conventions