You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Git WorktreesArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What
The 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.
Why
This 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.