Have you ever found a bug in your application, but been unable to find exactly *where* that bug was in your code?  Without this important bit of knowledge, it’s difficult to properly shame the developer that introduced the bug fix the bug.  It can be a bit like finding a needle in a haystack.   In…

I showed you one way that you can quickly see what’s changed back in Part 6 by comparing two commits.  You can also see what changed in a specific commit and fire up your git diff tool for each change.  I’ll show you how in this  post. [more] You can see a list of all…

One of my favorite git features is the ability to grab a commit and re-apply it on a different branch.  In this post, I’ll show you how to do this with the ‘cherry-pick’ command. [more] My team and I use a fairly standard git workflow.  Our master branch contains work that is actively under development. …

Today’s entry includes two tips for the price of one!  I’ll show you how to use git with Powershell to see all the files that changed between two commits.  I’ll also show you a quick and easy way to determine when a particular file was removed from source control. [more] First, let’s pretend that you…

Today’s simple tip will show you how to check for lingering “TODO” comments before you push your code up to your shared repository. [more] Have you ever dropped a TODO in your code to remind you to come back and refactor or clean something up later?  I’ll do that quite often when I’m hashing out…

Today’s tip is pretty simple.  I’m going to show you how you can break up a commit into multiple, smaller commits after you’ve already committed everything to your local repo. [more] I’m a big advocate of peer reviews.  I always try to think about the poor sap lucky soul that gets to review my changes. …

In my last post, I alluded to combining commits before pushing them to the shared repository.  The magic command that can make that happen is “rebase,” and I’m going to show you how I use it every day. [more] What is Rebase? First, let’s get something out of the way: history cannot be changed.  That’s…

Git’s flexibility allows you to use it however you want.  Your day-to-day workflow can be as complex or as simple as you decide to make it.   Here’s a “simple” workflow that my team and I use. [more] We have exactly two primary branches in our shared repository at any point in time: a release branch…