Git repos have lots of write protected files in the .git directory, sometimes hundreds, and the default rm my_project_managed_by_git will prompt before deleting each write protected file. So, to actually delete my project I have to do rm -rf my_project_managed_by_git.
Using rm -rf scares me. Is there a reasonable way to delete git repos without it?
Use rm -rf. If you are scared of mistakes, type
echo rm -rf nameofdirectory, check it, go back, delete theechoand press enter.use relative paths (cd into the directory below your repository) and use tab completion, and you won’t have problems.
honestly I don’t think there is a better way, like others have said you can use a trash program or you can chmod the git directory before deleting but, I would recommend against the comments saying alias the command, that can lead to even bigger problems if you typo thr alias or mess up in the script. rf can’t break anything unless you say the wrong directory which would be the same with aliases anyway,
My recommendation out of them all would be using a trash program to move it to the trash that way if you do screw up the location you have a way to restore it otherwise you could make a script to list the files affected using ls and then prompt a yes/no prompt using read before doing the rm script, but that’s something you definitely want to test in a sandbox or user restricted environment if you’re not used to scripting in case something breaks
Ah, yes, run a bash file executing
rm -rf $1What could go wrong?
Maybe use a graphical file manager?
Or move the folder to /tmp or so.
Or a tui file manager like
ncduThat’s a good suggestion for some, but I’m quite comfortable with the command line.
It’s not that I’m irrationally scared of
rm -rf. I know what that command will do. If I slow down an pay attention it’s not as though I’m worried “I hope this doesn’t break my system”.What I really mean is I see myself becoming quite comfortable typing
rm -rfand running it with little thought, I use it often to delete git repos, and my frequent use and level of comfort with this command doesn’t match the level of danger it brings.Just moving them to
/tmpis a nice suggestion that can work on anywhere without special programs or scripts.You don’t sound like you’re comfortable with the command line.
Just checked my command history and I’ve run 60,000 commands on this computer without problem (and I have other computers). I guess people have different ideas of what “comfortable” means, but I think I consider myself comfortable with the command line.
I have shot myself in the foot with
rm -rfin the past though, and screwed up my computer so bad the easiest solution was to reinstall the OS from scratch. My important files are backed up, including most of my dotfiles, but being a bit too quick to type and run arm -rfcommand has caused me needless hours of work in the past.I realized the main reason I have to use
rm -rfis to remove git repos and so I thought I’d ask if anyone has a tip to avoid it. And I’ve found some good suggestions among the least upvoted comments.I’m the same as you! I recommend “trash-cli”, then you can undo if you mess something up. You can even set an alias to echo “wrong command” if you use ‘RM’.
If you’re making backups of things you care about and not running
sudo rm -rfthe command isn’t really dangerous.But +1 for having it in /tmp I have a bash function I call tempd that is basically
cd $(mktemp -d)I use it so much for stuff I dont really care to keep.Never heard of mktemp before, that’s need. Come to think of it I never thought about how /tmp is really used by the system in the first place, time to do do studying I guess
chmod -Rthe directory first?This, lol just remove write protection if -f is too spooky
If you’re scared to do
rm -rf, do something else that lets you inspect the entire batch of deletions first. Such as:find .git ! -type d -print0 | xargs -0 -n1 echo rm -fvThis will print out all the
rm -fvcommands that would be run. It’s basicallyrm -rf --dry-run, butrmdoesn’t have that common option. Once you’ve verified that that’s what you want to do, run it again withoutechoto do the actual deletion. If you’re scared of having that in your history, either use a full path for .git, or prepend a space to the non-echo version of the command to make it avoid showing up in your shell history (assuming you have ignorespace in your HISTCONTROL env var)I use this
xargs echopattern a lot when I’m crafting commands that are potentially destructive or change lots of things.You should have backups. Preferably also snapshots. Then rm will feel less scary.
So… you’re afraid of the command that does the thing you’re trying to do?
More like, I’m afraid of the command doing more than I’m trying to do.
What I want to do is ignore prompts about write-protected files in the
.gitdirectory, what it does is ignore all prompts for all files.so why not
rm -rf folder/.git/*thenrm -r folder/*Generally that is not a concern because regular users won’t be able to
rmanything else other than those in his own $HOME.Another thing I want to say is, command line is for careful users. If someone is careless, they should create a wrapper around
rm, or just use a FM.That’s a good example. If I’m regularly running a command that is a single whitespace character away from disaster, that’s a problem.
Imagine a fighter aircraft that had an eject button on the side of the flight stick. The pilot complains “I’m afraid I might accidentally hit the eject button when I don’t need to”, but everyone responds “why would you push the eject button if you don’t want to eject?”, or “so your concern is that the eject button will cause you to eject…?” – That’s how I feel right now.
Are you regularly deleting git repos?
How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like “Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?”
In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that’s managed by the flight computer.
I understand the mindset you have, but trust me, you’ll learn (sooner or later) a habit to pause and check your command before hitting enter. For some it takes a bit longer and it’ll bite you in the butt for few times (so have backups), but everyone has gone down that path and everyone has fixed their mistakes now and then. If you want hard (and fast) way to learn to confirm your commands, use dd a lot ;)
One way to make it a bit less scary is to ‘mv <thing you want removed> /tmp’ and when you confirmed that nothing extra got removed you can ‘cd /tmp; rm -rf <thing>’, but that still includes the ‘rm -rf’ part.
deleted by creator
You just need to do this then
cd git-project rm -rf .git cd .. rm -r git-projectWith
rm-r is for ®ecursion and -f is for F(force) disabled the prompting. So, use -f on the .git directory which has the files you want to obliterate, and leave it off for the safety prompts.
Using rm -rf scares me. Is there a reasonable way to delete git repos without it?
I don’t know what to tell you, that’s the command you need to use.
If you’re that worried you’re going to nuke important stuff, make backups, and don’t use
sudofor user files.https://github.com/nivekuil/rip This is what you’re looking for
chmod -R 777 my_project_managed_by_git && rm -r my_project_managed_by_git
