The best upgrade to these kinds of git branch scripts is piping them to fzf. I’ve been using this fbr one from the fzf repo. <a href="https://github.com/jbranchaud/dotfiles/blob/main/zshrc.local#L38" rel="nofollow">https://github.com/jbranchaud/dotfiles/blob/main/zshrc.local...</a>
I have been using the `git lb` alias suggested by <a href="https://ses4j.github.io/2020/04/01/git-alias-recent-branches/" rel="nofollow">https://ses4j.github.io/2020/04/01/git-alias-recent-branches...</a> (post written April 1st but not a joke) and quite enjoying it. Shows me the last 10 branches I worked on (very easy to edit the alias definition to get more or fewer than 10), sorted by date, most recent first. It's been handy in all sorts of situations, especially because one of our internal libraries needs a bugfix or a new feature every 3 months or so. So every time I cd into that repo, I have no clue what I did last, but `git lb` tells me right away.
Even better (IMHO!) is `git config branch.sort -committerdate` (note the `-`). This will sort newest committer date first.
`git config --global branch.sort -committerdate`
Rebase an old branch and it suddenly looks recent again. The rewritten tip gets a fresh committer date.
Yes. This is what one wants, since if you have recently rebased it, you're clearly doing work with it. Meanwhile, branches you don't care to touch sink to the bottom of the list.
I would hope so
I have this as an alias in my .zshrc!! Very handy
Even better, "hey, chat GPT, list my branches by commit date."<p>I know that's not a popular answer, but I'm just trying to demonstrate the reality that this kind of knowledge isn't specialized anymore.
I made a lovely little TUI for this, with Charm (<a href="https://charm.sh" rel="nofollow">https://charm.sh</a>)<p><a href="https://github.com/tyre/recent-branches" rel="nofollow">https://github.com/tyre/recent-branches</a><p>Enjoy!
FYI/fwiw Fish shell autocompletes branches sorted by last commit date when writing out git commands. It also provides completions for commitish objects grouped by class, giving precedence to the usual targets first, with each group sorted by its own sort key. Handy!
Huge fan of `git recent` [0] for this purpose.<p>[0] - <a href="https://github.com/paulirish/git-recent" rel="nofollow">https://github.com/paulirish/git-recent</a>
Our team's `git branch` output is a graveyard. Sorting by last commit would be a godsend for quickly identifying active work and stale branches.
Such a small quality of life improvement. My `git branch` output is a graveyard sometimes, this would be handy.
I have been using something like this for 10+ years by this point - still wonder why it is not default or easier to do than a custom gitconfig/alias hack. :P
Probably because most of the time you list branches you goal isn't to discover what exists, but to find the specific one you're looking for.
> Just configure git branch to sort by the last commit date:<p>> git config branch.sort committerdate<p>> You can also supply this on a one-off basis as git branch --sort committerdate.<p>These don't seem like hacks to me. What do you have in mind?
I love this little fzf bash function that I wrote a few years ago: <a href="https://gist.github.com/thomasaarholt/141df779f3f16b641701b4782431f7c3" rel="nofollow">https://gist.github.com/thomasaarholt/141df779f3f16b641701b4...</a><p>It opens a fuzzy finder window showing the branches you have in the repo, sorted by recency. Also shows the latest committer and the date. Hit enter on the one you want to swap to it.
TIL Git can do this without a shell script. I’ve been manually sorting through branches like an idiot
Nice. Will help solve some mysteries on older projects.
nice. I made myself pretty much the same command couple years ago but called it 'latestbranches'.
How many branches would you need to have to make this worthwhile?
At any time I'm working across 5-30 branches (some when I'm reviewing other folks' code) so it's handy to see my latest branches
At my current job it's fairly frequent that I have 5+ active branches open for a repo. Not ideal and that's another topic, but it is nice to be able to sort branches because of that.
I've seen monorepos with over 10k active branches. But even at a smaller scale (10-100 branches), it becomes useful when manually stacking and/or rebasing, especially if you have a smaller terminal.
yep, i have a little helper in my zshrc for this sort of thing:<p>alias git-hot-refs="git branch --sort=committerdate | tail"
Or just have `jj log` custom-configured.
Let's sort git branches by quality, better branches towards the top, slop at the bottom.
Another useful one if you have a large number of tags and want to see the most recently created ones first:<p><pre><code> git config --global tag.sort -creatordate
</code></pre>
(`-creatordate` reverses the sort so that the newest come first.)
I just click on tower and open it, much better
Feels like the type of problem you could simply choose to not have in the first place (by not using git).
Amazing what one can learn from rtfm