{"version":"2.1.277","anchor":"new-attach-sync-safety-check-for-directory-sync-git-worker","canonical_anchor":"new-attach-sync-safety-check-for-directory-sync-git-worker","heading":"New attach-sync safety check for directory sync (git worker), gated by tengu_violin_soundpost","tier":"soon","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-attach-sync-safety-check-for-directory-sync-git-worker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New attach-sync safety check for directory sync (git worker), gated by tengu_violin_soundpost\n\nDirectory sync gains a pre-attach safety check to verify a checkout can attach cleanly, behind a new gate\n\n**Unclear.** No reading of the `tengu_violin_soundpost` gate has been taken, so whether it is active is unknown.\n\n**What**\n\nThe directory-sync git worker now has an `attachSyncEnabled` check that determines whether attaching to an existing remote or local checkout would succeed cleanly, before doing so. It returns one of several states: \"unanswered\", \"switched_off\", \"commit_not_held\", \"other_branch\", \"lines_up\", or \"not_in_history\". A companion function proactively re-triggers this check while sync is in a \"listening\" state.\n\n**Why**\n\nThis is meant to catch cases where a directory-sync checkout can't cleanly attach to the expected commit or branch before problems occur, rather than after. This behavior is controlled by a setting called `tengu_violin_soundpost`.\n\n- Area: Directory Sync\n- Names: `tengu_violin_soundpost`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}