Can you tell me why git seems to remember and use its “fetch memory” for a deleted local repository? I delete a local branch that was tracking a remote, and when that remote is completely replaced and I check it out and track it locally, I’m getting the original local/remote code (without updates/changes) if I don’t fetch first. Why does this happen? Why does git keep the original outdated branch version after the local branch was deleted? Thank you for you help!
hiya - One possibility I can think of is that the local code will not be deleted immediately when the branch is deleted. It would only be removed on garbage collection in 90 days. And then when we checkout we are not performing a pull/fetch from the new remote and simply refering to the existing old local code.
VisualGit is fantastic! What do we have to do to get it working on macOS and Linux?
Thanks! Working on this at the moment :-) Cheers Mark
nice visual representation !
Thank you! Cheers!
Have made the tool available so you can experiment yourself on a local repo now too:
visualgit.net
Can you tell me why git seems to remember and use its “fetch memory” for a deleted local repository? I delete a local branch that was tracking a remote, and when that remote is completely replaced and I check it out and track it locally, I’m getting the original local/remote code (without updates/changes) if I don’t fetch first. Why does this happen? Why does git keep the original outdated branch version after the local branch was deleted? Thank you for you help!
hiya - One possibility I can think of is that the local code will not be deleted immediately when the branch is deleted. It would only be removed on garbage collection in 90 days. And then when we checkout we are not performing a pull/fetch from the new remote and simply refering to the existing old local code.