{"version":"2.1.265","anchor":"dir-sync-git-worker-turn-end-telemetry-gains-an-unchanged","canonical_anchor":"dir-sync-git-worker-turn-end-telemetry-gains-an-unchanged","heading":"dir-sync git-worker turn-end telemetry gains an 'unchanged' outcome and a report toggle","tier":"internal","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/dir-sync-git-worker-turn-end-telemetry-gains-an-unchanged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### dir-sync git-worker turn-end telemetry gains an 'unchanged' outcome and a report toggle\n\nDirectory-sync turn-end telemetry adds an 'unchanged' outcome and a way to skip reporting\n\n**What**\n\nThe internal function that reports on the directory-sync git worker at the end of a turn now takes a third parameter (defaulting to true) that controls whether the `ccr_dir_sync_git_worker_turn_end` telemetry event fires at all. Its success branch, which previously matched 'shipped' or 'nothing_to_send', now also matches a new 'unchanged' outcome.\n\n**Why**\n\nThis is internal telemetry refinement for the directory-sync system, distinguishing a turn where nothing changed from one where changes were sent, and allowing that reporting to be turned off when not needed.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}