{"version":"2.1.282","anchor":"git-dir-move-detection-also-compares-directory-birth-time","canonical_anchor":"git-dir-move-detection-also-compares-directory-birth-time","heading":"A deleted and recreated Git folder is now recognised as a different one","tier":"internal","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/git-dir-move-detection-also-compares-directory-birth-time","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### A deleted and recreated Git folder is now recognised as a different one\n\nWhen checking whether a Git folder has moved, Claude Code now also compares its creation time, so a recreated folder counts as moved\n\n**Unclear.** Which feature relies on this moved check is not known.\n\n**What**\n\nClaude Code remembers the identity of a repository's Git folder so it can tell later if it has moved. It now also compares the folder's creation time with the one it recorded, when one was recorded. A Git folder that was deleted and recreated, even one that looks the same to the operating system, is now treated as moved.\n\n**Why**\n\nThis stops Claude Code treating a recreated repository as the same one it saw before.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}