git rm -rf is only usable within the scope of the git repository and removes files in the staging area and working directory but doesnt affect untracked files or .git. rm -rf affects everything. For this case rm -rf probably would be the better option
rm - rf is the only version that makes sense, since the only reason to delete and re-clone is to recover from an unexpected .git/ state, and git rm won’t remove that.
I feel dumb: Why
git rm -rfand notrm -rf? O.ogit rm -rfis only usable within the scope of the git repository and removes files in the staging area and working directory but doesnt affect untracked files or .git.rm -rfaffects everything. For this caserm -rfprobably would be the better optionNever heard of it, makes total sense, but I’d guess 95% of developers just nuke the directory raw.
That’s the joke, yes.
Thanks
rm - rfis the only version that makes sense, since the only reason to delete and re-clone is to recover from an unexpected.git/state, andgit rmwon’t remove that.