NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
Sort branches by last commit date (ryangreenberg.com)
jbranchaud 49 minutes ago [-]
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. https://github.com/jbranchaud/dotfiles/blob/main/zshrc.local...
asb 6 hours ago [-]
Even better (IMHO!) is `git config branch.sort -committerdate` (note the `-`). This will sort newest committer date first.
mmsc 3 hours ago [-]
`git config --global branch.sort -committerdate`
hsuduebc2 19 minutes ago [-]
Thanks!
nulltrace 3 hours ago [-]
Rebase an old branch and it suddenly looks recent again. The rewritten tip gets a fresh committer date.
seattle_spring 4 minutes ago [-]
I would hope so
quuxplusone 2 hours ago [-]
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.
johnwheeler 1 hours ago [-]
Even better, "hey, chat GPT, list my branches by commit date."

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.

hsuduebc2 18 minutes ago [-]
Heh. "Just Google it" answers we're never particular conversation lubricant as they are not now. But of course you are right we live in age of wonder once again.
pkaodev 6 hours ago [-]
I have this as an alias in my .zshrc!! Very handy
m4rtink 20 minutes ago [-]
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
dataflow 7 minutes ago [-]
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.
fwip 13 minutes ago [-]
> Just configure git branch to sort by the last commit date:

> git config branch.sort committerdate

> You can also supply this on a one-off basis as git branch --sort committerdate.

These don't seem like hacks to me. What do you have in mind?

ComputerGuru 5 hours ago [-]
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!
cryptolobster 28 minutes ago [-]
TIL Git can do this without a shell script. I’ve been manually sorting through branches like an idiot
metmac 5 hours ago [-]
Huge fan of `git recent` [0] for this purpose.

[0] - https://github.com/paulirish/git-recent

metmac 5 hours ago [-]
Spoiler it’s fzf under the hood. But it’s perfect and simple.
dalton74 2 hours ago [-]
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.
rglover 25 minutes ago [-]
Nice. Will help solve some mysteries on older projects.
Trace88 2 hours ago [-]
Such a small quality of life improvement. My `git branch` output is a graveyard sometimes, this would be handy.
Waterluvian 1 hours ago [-]
Sorting alphabetically never made sense and basically represents not trying to do something useful with the ordering of branches.
tomtom1337 5 hours ago [-]
I love this little fzf bash function that I wrote a few years ago: https://gist.github.com/thomasaarholt/141df779f3f16b641701b4...

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.

matltc 35 minutes ago [-]
Amazing what one can learn from rtfm
zahlman 5 hours ago [-]
How many branches would you need to have to make this worthwhile?
jamietanna 5 hours ago [-]
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
spike021 3 hours ago [-]
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.
woodruffw 5 hours ago [-]
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.
mcdow 3 hours ago [-]
yep, i have a little helper in my zshrc for this sort of thing:

alias git-hot-refs="git branch --sort=committerdate | tail"

tikhonj 1 hours ago [-]
Let's sort git branches by quality, better branches towards the top, slop at the bottom.
monster_truck 5 hours ago [-]
I just click on tower and open it, much better
bewareofscams 6 hours ago [-]
Or just have `jj log` custom-configured.
woodruffw 5 hours ago [-]
Another useful one if you have a large number of tags and want to see the most recently created ones first:

    git config --global tag.sort -creatordate
(`-creatordate` reverses the sort so that the newest come first.)
jeffbee 3 hours ago [-]
Feels like the type of problem you could simply choose to not have in the first place (by not using git).
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 01:38:00 GMT+0000 (Coordinated Universal Time) with Vercel.