Right now the `g, performing a {nav Git rm`emove}" operation uses `--force`on on the file destroys it, which is dangerous because it canpassing
destroy your files in the case where you accidentally stage athe `--force` option, which is dangerous because it can destroy your file whes in then want it case
un-where you accidentally staged. Right now, a file when then want it un-staged. performing a {nav Git remove}" operation onBecause the file destroys it.was
Because the file was not yet added to the history, it's not recoverable. And because the file was was deleted
file was was deleted using `git`, it's not put in the trash or made an undoable operation.
This patch fixes that by replacing the `--force` argument with `--cached`, which uses
a safe behavior by default and keeps the file on disk rather than destroying it.
As a result, removed files must be manually deleted, moved to the trash, etc. Arguably
this is saner, more user-friendly behavior in general, especially for the kind of person
who prefers to use a GUI tool to interact with git.
BUG: 414342
FIXED-IN: 19.12.0