{"version":"2.1.232","anchor":"directory-sync-can-check-its-base-against-a-remote-ref","canonical_anchor":"directory-sync-can-check-its-base-against-a-remote-ref","heading":"Directory sync can check its base against a remote ref","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/directory-sync-can-check-its-base-against-a-remote-ref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Directory sync can check its base against a remote ref\n\nDirectory sync can compare against a remote git reference and refuses invalid object ids.\n\n**What**\n\nThe directory sync path can now build its comparison base from a remote reference by listing the cloned tree with `git ls-tree -r -z --full-tree` under `GIT_NO_LAZY_FETCH=1`, and refuses when the tree or commit is not a valid object id.\n\n**Details**\n\n- It reads `core.filemode` to decide whether file modes from the listing can be trusted.\n- The stored-base validator now rejects malformed tree references with a message about a sync base naming a path or commit its reader would refuse.\n- Only the directory sync path uses this; nothing else in the build reaches it.\n\n**Evidence**\n\n`sync base names a path or commit its reader would refuse`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}