I suppose it makes sense that when you work for a company everyone assumes you know everything about using its products. When I worked at Symantecs Managed Security Services people asked me all the time how to use the antivirus. It’s a normal assumption, even if it’s off base.
So working at GitHub I get asked git & GitHub questions all the time. #REALTALK: The fact is I’m not a great Git user. I don’t rebase. I’m terrible about using bisect. I had to squash a commit once and it took me an embarrassingly long time.
There are all kinds of features I know exist but hardly ever use. That said I know about 90% of what I need to use Git effectively, and I’ve gotten pretty good at GitHub (the product) itself. So here’s where I learned and what I think will help you get the most out of Git and GitHub.
Just in case you don’t know what Git is here is a formal intro:
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.
To learn Git I recommend starting out with TryGit. This is a quick, 15 min tutorial that introduces the core concepts of Git that you’ll need and is enough to get started. It’s pretty much the ideal place to start, and you don’t even need to install anything.
TryGit is certainly enough to get yourself started, but eventually you’ll want to move on to some of the more advanced command line options. To learn those I recommend Git Immersion. Git Immersion is actually done on your own system’s command line and teaches things like rebasing vs merging, tagging, and even resolving merge conflicts.
Between those resources you’ll have a pretty solid base in using Git. Those concepts will get you most of the way towards using GitHub effectively, but GitHub does add a few concepts on top of Git such as Comments, Issues & Pull Requests, and Releases.
At it’s core the most important part is what we call “The GitHub Flow”:
- The master branch is always deployable. Always.
- Create a branch from master of a repository you want to contribute to.
- Make commits to the code in the branch.
- Push the branch back up to GitHub, you’ll get an interface to create a Pull Request.
- You (and the other contributors to the repo) can now commit more code, discuss changes using comments, and finalize the code.
- At this point a repo owner can merge the changes.
There’s an even better graphical introduction of the GitHub Flow here. Want one more blog based take? I really like Mark Otto’s Some GitHub Flow writeup that covers each step in great detail. No matter which guide you read if you can master those 5 steps you’ll be a GitHub master.
Being Even more Awesome at GitHub#
Now that you’ve learned Git and the key elements of the “GitHub Flow” there are still more fun things to learn:
- Make some of those Git actions even simpler and more tightly coupled to GitHub using GitHub’s native clients. Check it out for Mac & Windows.
- Learn GitHub Flavored Markdown to write great structured documentation. GHFM also works in Issues and PRs.
- Start using Issues to track bugs and enhancements.
- Emoji!!! Not just for your smartphone, you can use them anywhere you use GitHub Flavored Markdown.
- Learn GitHub’s keyboard shortcuts. Hint: start by pressing
- Take a look at ways to build great personal & project specific sites using GitHub Pages.
- And more!
I gave a presentation a few years ago about this, give it a look, but even better just go try it!
Looking for More#
- GitHub Guides — In-depth documentation about using Git & GitHub.
- GitHub Training — GitHub’s Training team puts on great classes & workshops, many of which are free!
- GitHub Training YouTube Channel — An amazing group of videos teaching many of these concepts by video with some of GitHub’s excellent trainers.