You'll notice
--force-remove-worktree help text now clarifies its 'no uncommitted changes' rule covers submodules too
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.