Looks like I am the one with the late article this week. Hopefully it is worth the wait for some of you.
As mentioned in my article last week I’m going to go through how to setup a similar workflow to what I use here at Gaslamp Games. Before I get ahead of myself I should probably start at the beginning for those who might stumble on this post with very little previous experience with git. This article assumes you know your way around a Linux command line and can install packages on your system with no problem.
So what is git?
Git is a “free & open source, distributed version control system” and while that may be a quick blurb about what git is, it is exactly what it says. Every time you clone a git repository (more on that later) you not only get the entire repository but you get every commit, a full history, and my favorite part; once cloned there is no need to have a central server or even network access. This allows me to pull the latest changes, pack up my laptop and head somewhere excluded when I need to really get some work done. There is quite a bit to know about exactly how git works but that is well beyond the scope of this article. If you are curious how exactly how it all works I would suggest you get a cup of coffee and see the excellent video over at gitcasts I referenced last week.
