Ah git. Git is powerfully ferocious utility for version control of the code for a software project, but you must tame the beastly demon of experience by coming to sumbling blocks, getting through them, and documenting how you did it. So, let's do it...
This is a great little tip for any software developer, regardless of your programming language of choice. It's these subtle things that can raise you up regular programmer to coding superstar. When sending URLs that link to files on github you may want to reference a specific line number or block of code. The people receiving your code snippets will appreciate these nice highlights, and (subconsciously or not) they'll be thinking, "damn, he's good".
If you have multiple accounts on Github (or whatever git repository host you use) then it can be a little confusing knowing which user you are committing as and how to switch to a different user. In this post I'll show you an easy way to switch between users from the command line.
I personal like the control you have when using git from the command line, and a nice thing to be able to do is see the changes I've made (duh hehe). I really didn't know the proper name for this so I am calling it the "git commit lifecycle", but basically these are shell scripts you can run to see your changes before you add the changes, after you add them but before committing, and after committing. Enjoy!
This is something I've had to do quite a few times, but it wasn't until I worked on a bunch of Github projects at HBO that I really started to get understanding branching in git. In my own Github projects I would often work right out of the master branch. This is fine for developers who are just getting started with git, but when working on large, enterprise projects you really want to be smart about using branches. This post will help you understand making git branches off of existing branches.
The posts on this site are written and maintained by Jim Lynch. About Jim...