Books. Preface. Git is a version control Swiss army knife. A reliable versatile multipurpose revision control tool whose extraordinary flexibility makes it tricky to learn, let alone master. As Arthur C. Clarke observed, any sufficiently advanced technology is indistinguishable from magic. This is a great way to approach Git: newbies can ignore its inner workings and view Git as a gizmo that can amaze friends and infuriate enemies with its wondrous abilities. Rather than go into details, we provide rough instructions for particular effects. After repeated use, gradually you will understand how each trick works, and how to tailor the recipes for your needs. I’m humbled that so many people have worked on translations of these pages.
Dustin Sallings, Alberto Bertogli, James Cameron, Douglas Livingstone, Michael Budde, Richard Albury, Tarmigan, Derek Mahar, Frode Aannevik, Keith Rarick, Andy Somerville, Ralf Recker, Øyvind A. François Marier maintains the Debian package originally created by Daniel Baumann. 25 Tips for Intermediate Git Users : Andy Jeffries : Ruby on Rai. I’ve been using git for about 18 months now and thought I knew it pretty well. Then we had Scott Chacon from GitHub over to do some training at LVS, a supplier/developer of betting/gaming software (where contracted until 2013) and I learnt a ton in the first day.
As someone who’s always felt fairly comfortable in Git, I thought sharing some of the nuggets I learnt with the community might help someone to find an answer without needing to do lots of research. 1. First Steps After Install After installing Git, the first thing you should do is configure your name and email, as every commit will have these details: $ git config --global user.name "Some One" $ git config --global user.email "someone@gmail.com" 2. Everything stored in git is in a file. From there branches and tags are simply files containing (basically) a SHA-1 hash which points to the commit. You may have heard references to the HEAD. 3. 4. By now I’m sure you have had a merge conflict and had to resolve it. 5. 6. 7. 8. 9. 10.
Learn git one commit at a time. Why You Should Switch from Subversion to Git. Table of Contents. Preface.