Sort git Branches by Date
I'll be first person to admit I don't do as much git repository maintenance as I should. I rarely delete branches which have been merged, so a git branch execution shows me a mile-long list of branches that likely aren't relevant. The best way to find branches I've recently used is to use the following command:
git for-each-ref --sort=-committerdate refs/heads/
The command above lists the most recently worked on branches from top to bottom. If you want to see the date of last commit, you can do this:
git for-each-ref --sort='-committerdate' --format='%(refname)%09%(committerdate)' refs/heads | sed -e 's-refs/heads/--'
I find these commands incredibly helpful when returning to work from a weekend or just jumping from project to project. Hopefully you can use these commands too!
![Write Better JavaScript with Promises]()
You've probably heard the talk around the water cooler about how promises are the future. All of the cool kids are using them, but you don't see what makes them so special. Can't you just use a callback? What's the big deal? In this article, we'll...
![CSS Gradients]()
With CSS border-radius, I showed you how CSS can bridge the gap between design and development by adding rounded corners to elements. CSS gradients are another step in that direction. Now that CSS gradients are supported in Internet Explorer 8+, Firefox, Safari, and Chrome...
![Create a Trailing Mouse Cursor Effect Using MooTools]()
Remember the old days of DHTML and effects that were an achievement to create but had absolutely no value? Well, a trailing mouse cursor script is sorta like that. And I'm sorta the type of guy that creates effects just because I can.
![Fixing sIFR Printing with CSS and MooTools]()
While I'm not a huge sIFR advocate I can understand its allure. A customer recently asked us to implement sIFR on their website but I ran into a problem: the sIFR headings wouldn't print because they were Flash objects. Here's how to fix...
I use this version to show latest git branches with the timestamp as a relative/human readable format:
Hey man, I used your snippet and noticed after a while that it actually gets the timing wrong. For example a branch I created today is showing as being worked on 2 weeks ago
That might be because the timestamp doesn’t show the branch creation time but the commit time of the last commit of the branch.
I’m definitely going to bookmark this as I’m using git more and more in team settings where we will probably be branching a lot more. This will come in handy.
Super-helpful even three years on — thank you!
FWIW, I found it much easier to read by putting the date first, as in Amy’s example. That also allows for reverse sorting if desired.
This is gold, thanks a lot!
So helpful! I’ve accumulated dozens of branches in my main project over the years. Sorting them by date, and seeing the dates, is super helpful when trying to purge the useless ones while still keeping around some of the just-in-case guys.
Good feature, thanks a lot!
Also I add that you can add this command to .gitconfig e.g. like a “lastbrs” (last branches) and add the flag “–count” to prevent display all the branches.
You can also just do
git branch --sort=-committerdateto get the local branches with the most recently committed to on top.Also, forgot to mention. If you want this to be the default sort order for all your repositories. Just do
git config --global branch.sort -committerdate.After that a regular call to
git branchwill sort like this.