Git 2.56's fetch.followRemoteHEAD setting fixes stale origin/HEAD for every remote

DEV Community·5 points·alexgeorgiev17·about 4 hours ago·dev.to

Git 2.56 adds a global fetch.followRemoteHEAD default: one config line kept origin/HEAD correct across 3 separate remotes in my tests, where the identical line did nothing on Git 2.55.

Read the full article at dev.to →

#git #fetch #followremotehead #head #origin #56s #stale #fixes

Related stories

git-kv: Key-value store attached to git commits using Git notesgithub.com
Lobsters · 13 points · 6 months ago
I wrote Git objects by hand until real Git stopped complainingdev.to
DEV Community · 6 points · 7 days ago
Git-bug: Distributed, offline-first bug tracker embedded in Gitgithub.com
Hacker News · 357 points · 7 days ago
Ask HN: Do we still need code editors, or are Git clients enough?
Hacker News · 1 points · 12 days ago
Laya vs Jev head-to-head on identical inputsgithub.com
Hacker News · 1 points · 10 days ago
Show HN: EnvSeal-CLI – Git for Secrets, Offline Git-Native Secret Managergithub.com
Hacker News · 2 points · 10 days ago

Related topics

vcs25 code433 ai2303 github95 history92 source302 management46 rust253 agent495 worktree4 agents485 storage31