Git was one of those technologies that I have been aware of for a while. I knew that I needed to learn it as it has become a standard in the industry, but I fought it until I couldn’t anymore. In fact, I signed up for my Github account several years ago and started playing around with creating code repositories, forking repositories, and cloning repositories. I even did more than one online tutorials. However, I still struggled to grasp the concepts and processes required to be successful. I finally reached out to a good friend in the industry and asked him if he could share his Git process. Upon him agreeing to share it with me, we got started and I took notes on every single step of it. I even went as far as posting sticky notes on the wall next to me as well as wrote the process out on a whiteboard. I then made a commitment to learning it and started moving all of my projects into GitHub. I then practiced and practiced until my Git deployment process became second nature to me.
Today, I couldn’t be happier that I stuck with it. I even use a tool called DeployHQ to deploy sites from my GitHub repo to a production site.
However, I have learned some hard lessons along the way. Just recently, I was copying a project from one project to another and didn’t realize I also copied the .git file. So, I went to commit and push to my new repo on Github and had a total panic attack when I realized that I pushed my new project to the wrong repo. Thank goodness for Tower. I know I could have fixed it with git reset and or git revert… However, Tower made it a lot less painful and saved me a lot of time.
Another, little funny side effect of getting into git, I have more than once typed the word ‘git’ instead of ‘get’ when writing emails. Ie. ‘Hey, we should git together this weekend after the game…’