{"version":"2.1.274","anchor":"worktreejob-deletion-now-detects-in-progress-submodule-work","canonical_anchor":"worktreejob-deletion-now-detects-in-progress-submodule-work","heading":"Worktree\/job deletion now detects in-progress submodule work before removing","tier":"notice","area":"Git Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/worktreejob-deletion-now-detects-in-progress-submodule-work","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Worktree\/job deletion now detects in-progress submodule work before removing\n\nDeleting a job's worktree now checks for in-progress submodule work before removing it, instead of only tracked-file state\n\n**What**\n\nWhen Claude Code deletes a job and cleans up its associated git worktree (a separate working copy tied to a branch), it now also checks the status of any git submodules. If submodule state can't be verified, the worktree is kept rather than deleted, with a new 'submodule' reason recorded for why it was kept. Previously this check only looked at whether tracked files were dirty or whether there was a nested repository.\n\n**Why**\n\nThis avoids accidentally deleting a worktree that has in-progress or unverifiable submodule work, reducing the risk of losing uncommitted changes inside a submodule.\n\n- Area: Git Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}