git branch -D force-deletes an unmerged branch

Deletes a branch even when its commits are not merged anywhere, so the work becomes unreachable. This rule is CASE-SENSITIVE on purpose and that is why it uses detail_contains: -D force-deletes while -d refuses to delete unmerged work, and the engine's regex matcher is case-insensitive, so a regex here would fire on the safe spelling every time a developer cleans up after a merge. Known miss: the flags written separately as --delete --force in the reverse order, and any alias. The git branch anchor tolerates repeated or tab whitespace and a global flag in between (git branch -D …, git -C <dir> branch -D …), and an absolute tool path such as /usr/bin/git still matches, while -D stays a case-sensitive substring so the safe -d is not caught. A quoted MENTION is not a use: a search, a git commit -m message, an echo or a curl --data body that only names this command is left alone. That holds only while every shell metacharacter stays inside the quotes, so git commit -m "x" && … is still caught; and the carrier must be the first word, so sudo grep … is not exempt.