With a tool as rich as Git, it’sor to stop looking beyondThe risk is even greater when you come from a self-styled version management tool (say, Subversion) that actually only offers a tiny set of features: not only can you get confused with, but you have, so it’s hard to understand why Git behaves the way it does.The best way toabout its numerous commands and capabilities is to start by exploring its. Why do we haveinstead of 2? What is theanyway? What even isand why does it show up all over the place? Why do we talk about a history? How ismanagement different?Thanks to a solid understanding of Git’s core tenets, you’ll find that mechanisms such as branches, resets, cherry-picks, merges and rebases suddenly make a lot more sense…(Ce cours est également disponible en français .)