Getting Started with Git (and the Hub)
I’m very new to Git, but I find some of its features interesting and worth a post about. This is possibly a part 1 of more to come as I learn more about Git and how to use it effectively. The comments below are made with having mostly used SVN in the past for source control.
Features (that appeal to me):
These features are of DVCS in general, Bisect may be git specific.
- Local Commits – Even if you don’t have access to the repository, you’re still able to commit to your local copy. So even without commit access, you still have all the tools a cm system provides available to you.
- Entire revision history stored locally. – Let’s face it, hard drive space it cheap these days, and network hiccups happen from time to time. It’s nice to be able to have your revision history there when you need it. With SVN, without a path to the server there is little you can do.
- Bisect – While I haven’t used this, it seems like a very interesting feature. It allows you to specify a start and a stop revision. It then helps you track down when a bug was introduced. I may include something more about this after I’ve used it, but it still looks like an interesting feature.
Make sure you have git installed before starting here. I’m assuming git is installed, and you are a little familiar with the commands. Here are some links to some excellent resources to get you started if you’re not at that point yet:
- When starting out with any new command line tool, I see if there is a cheatsheet online for it. It’s always good to help you get acquainted with some of the commands. In general, a good starting point.
- This is a really cool resource I found while on my adventures in git. It helped me figure out how to revert files, which wasn’t entirely clear from the commands.
- It was useful to see some of the svn commands that I’m used to, and their git counterparts.
Well, now that you’re somewhat familiar with git, let’s get started on with github. Now, the main reason for posting this is because as a new user it didn’t seem that clear what I need to do to actually push to a repository. After you’ve been given access to, or created, a github repository, you must set your username and email for github to use.
Instructions on that can be found here: http://github.com/guides/tell-git-your-user-name-and-email-address
Now, here is the part that really wasn’t clear to me. You need to setup an ssh key to github as part of their authentication. I don’t know if this is correct, but I think of this as a layer of encryption that happens to make sure my files get to github unaltered. (similar to PGP for email)
Instructions for this can be found here: http://github.com/guides/providing-your-ssh-key
Now that you’re all setup, you’re ready to do some commits and then a push to the server. Have fun in the world of git.
In: Uncategorized · Tagged with: git, source control, svn