{"version":"2.1.277","anchor":"cloudremote-directory-sync-empty-git-start-now-distinguis","canonical_anchor":"cloudremote-directory-sync-empty-git-start-now-distinguis","heading":"Cloud\/remote directory-sync 'empty git start' now distinguishes detached vs attached sessions and checks reflog","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/cloudremote-directory-sync-empty-git-start-now-distinguis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Cloud\/remote directory-sync 'empty git start' now distinguishes detached vs attached sessions and checks reflog\n\nCloud directory-sync's initial-checkout logic now distinguishes detached from attached sessions and checks the reflog\n\n**What**\n\nThe logic that determines the starting state of a git checkout when syncing a sandbox or cloud checkout now explicitly tracks whether the branch is detached (has no branch name), and records this along with an origin value in its telemetry. It also now checks for matching refs under both the existing turns-ref prefix and a new second ref prefix, and checks whether a HEAD reflog exists, before deciding whether a checkout should be treated as 'unborn' (no commits yet) or 'committed'.\n\n**Why**\n\nThis makes the sync system's judgment about a fresh checkout's state more accurate, covering detached-branch sessions and an additional ref location that weren't distinguished before.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}