Git

Pull Requests are used often in the open source world, but less so on private teams. They are a great way to provide an automatic, team-wide code review mechanism. If your private team doesn’t use pull requests, I’d encourage you to investiage it. Why would you move your team over to pull requests? it provides a mechanism for code and source control review it gives more visibility and accountability to the whole team you can (optionally) restrict access so only trusted members bless the merge What is the Pull Request process like? There are lots of resources about how to submit pull requests out there, but the basics go like this. ...

About a week ago, we had an elusive error that appeared when we deployed our latest app to staging. Suddenly, any submission resulted in a “Stack trace too deep” error that gave no meaningful way to determine where the issue was coming from. We were stuck for a couple of days, but then I was reminded of git bisect. git bisect is a great way to trace down problems to a specific commit for purposes of isolation or blame (though I’d suggest against the latter). Like you’d expect from a programmer, it even searches efficiently, using a binary search, hence bisect. ...

Peepcode has a blog and it is managed in a very efficient and unique way. Everything is checked into git and pushed, no database involved–it’s kindof incredible. Check out the stack here: About this Blog | Free PeepCode Blog.

I recently converted all of my professional projects over to github and switched my dev workflow to use git. Oh, what a difference a tool makes. First off, git just works. It’s awesome to be able to switch branches super easily… and even create a branch after you’ve begun work on it. Realizing that you’ve started a new feature and need it to be in it’s own “silo” is great. What you want is for it not to be a pain to merge it back together. Honestly, I wish we had this at my old job where having multiple levels and several branches would have been highly beneficial. ...

Version Control Systems are critical when it comes to keeping your code in a place you can actually use it. Git is one of those systems that will change how you think about VCS because it suddenly makes it easy and fast to branch and merge. Become more efficient at git and quit wasting time with Subversion merges and remote repositories: 25 Tips for Intermediate Git Users