{"version":"2.1.265","anchor":"cloud-sync-snapshot-builder-gains-a-heldtree-parameter-and-b","canonical_anchor":"cloud-sync-snapshot-builder-gains-a-heldtree-parameter-and-b","heading":"Cloud sync snapshot builder gains a heldTree parameter and basis-aware 'lacking' handling","tier":"internal","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/cloud-sync-snapshot-builder-gains-a-heldtree-parameter-and-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Cloud sync snapshot builder gains a heldTree parameter and basis-aware 'lacking' handling\n\nCloud sync snapshot builder adds a heldTree option for tracking which files are missing\n\n**Unclear.** The finding doesn't say what `heldTree` represents conceptually or what user-visible effect this has on sync behavior.\n\n**What**\n\nThe internal function that builds a git snapshot (covering checkout, head, basis, and parent commits) for cloud and remote sync now accepts a new `heldTree` option, which is validated as a git object id. It uses this to work out which file paths are \"lacking\" relative to both the basis and the held tree, adding an extra asynchronous check before deciding what stays staged.\n\n**Why**\n\nThis refines how the sync process figures out which files are missing or need attention when building a snapshot, by comparing against an additional reference point (the held tree) rather than just the basis.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}