{"version":"2.1.248","anchor":"git-journal-distinguishes-a-cleared-copy-from-an-empty-one","canonical_anchor":"git-journal-distinguishes-a-cleared-copy-from-an-empty-one","heading":"Git journal distinguishes a cleared copy from an empty one","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/git-journal-distinguishes-a-cleared-copy-from-an-empty-one","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Git journal distinguishes a cleared copy from an empty one\n\nThe session git journal can now tell a cleared worktree copy apart from one that started empty.\n\n**What**\n\nThe per-session git journal gained files marking that a session ended and that it started empty, plus a hook and queue state for recording that a worktree copy was cleared, so an empty directory is no longer ambiguous.\n\n**Evidence**\n\n`markCopyCleared`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}