{"version":"2.1.242","anchor":"bridge-sessions-snapshot-the-state-of-the-git-working-tree","canonical_anchor":"bridge-sessions-snapshot-the-state-of-the-git-working-tree","heading":"Bridge sessions snapshot the state of the git working tree","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/bridge-sessions-snapshot-the-state-of-the-git-working-tree","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Bridge sessions snapshot the state of the git working tree\n\nSessions bridged from another environment record the git working tree state when they start.\n\n**What**\n\nSessions bridged from another environment now record a picture of the repository at startup, which explains how those sessions decide what state they resumed into.\n\n**Details**\n\n- Records branch, head commit, count of commits not pushed to `refs\/remotes\/origin\/<branch>`, whether the tree is dirty, whether an upstream exists, whether a rebase, merge, cherry-pick, revert or bisect is in progress, whether submodules exist, and whether Git LFS is in use.\n- LFS is detected by scanning the first 64 KiB of `.gitattributes` for `filter=lfs`.\n- The whole probe runs under a timeout; timing out reports \"worktree probe timed out\" and counts as a collection failure.\n\n**Evidence**\n\n`bridge_worktree_state`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}