Welcome to yet another Git tutorial, because let’s be honest with ourselves: there aren’t enough of them.<\/p>\n\n\n\n
Another name for this series might be “Learning Git: I try things that don’t work, so that you don’t have to”. I’ve had several start-stop relationships with Git over the last few years, and for this most recent effort I decided I was going to go all-out; deep-dive; and write up my learning experience afterwards in a way that I wished I could have learned it the first time.<\/p>\n\n\n\n
For many folks learning Git, the first command they are introduced to is clone<\/strong><\/em>. I’m going to do it differently: In four chapters and four appendices, the last <\/strong>command we’ll talk about is clone – by which time, hopefully, we’ll know exactly what it does and why.<\/p>\n\n\n\n I’m starting a new project, cow-tipper, and I would like to leverage source control. I’m going to use Git. I have my project directory containing my source files, so all I need is a repository.<\/p>\n\n\n\n My experience installing Git can be read here: Appendix A: Installing Git.<\/a><\/p>\n\n\n\n Part 1: The Basics<\/a><\/p>\n\n\n\n Part 2: Branching<\/a><\/p>\n\n\n\n Part 3: Remotes<\/a><\/p>\n\n\n\n Part 4: Remotes II – Reverse the Polarity!<\/a><\/p>\n\n\n\n Appendix A: Installing Git<\/a><\/p>\n\n\n\n Appendix B: Customizing the Git Message Editor<\/a><\/p>\n\n\n\n Appendix C: Petra Rabbit’s Authentication-palooza<\/a><\/p>\n\n\n\nThe Full Series:<\/h3>\n\n\n\n