{"version":"2.1.274","anchor":"force-remove-worktree-help-text-now-mentions-submodules","canonical_anchor":"force-remove-worktree-help-text-now-mentions-submodules","heading":"--force-remove-worktree help text now mentions submodules","tier":"notice","area":"Git Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/force-remove-worktree-help-text-now-mentions-submodules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### --force-remove-worktree help text now mentions submodules\n\n--force-remove-worktree help text now clarifies its 'no uncommitted changes' rule covers submodules too\n\n**What**\n\nThe command-line help text for `--force-remove-worktree` now clarifies that its safety requirement of having no uncommitted changes applies to tracked files, including submodules.\n\n**Why**\n\nThis makes the existing safety rule clearer, so users understand that submodule changes count toward blocking a forced worktree removal, not just changes to regular tracked files.\n\n- Area: Git Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}