{"version":"2.1.281","anchor":"new-git-entry-validation-for-folder-seeding","canonical_anchor":"new-git-entry-validation-for-folder-seeding","heading":"New .git entry validation for folder seeding","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-git-entry-validation-for-folder-seeding","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New .git entry validation for folder seeding\n\nA new check inspects .git entries when seeding a folder and refuses linked index files, unknown entries, oversized folders or missing config\/HEAD\n\n**Unclear.** The finding does not say what folder seeding is, and only suggests that this check backs the existing refusal message.\n\n**What**\n\nA new check examines each `.git` entry (the hidden folder where git keeps a project's history) when seeding a folder. It refuses:\n\n- Index files that are symlinked or hardlinked (links pointing to another file).\n\n- Entries it does not recognise.\n\n- `.git` folders that are too large.\n\n- Folders missing their config or HEAD file.\n\nIt seems to be what triggers the existing message \"has a .git entry that could not be read as a git checkout\".\n\n**Why**\n\nOnly `.git` folders that look like normal, self-contained git checkouts get past this check.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}