Can I remove a git repo without resorting to `rm -rf` ?
from Buttons@programming.dev to linux@lemmy.ml on 13 Jun 23:24
https://programming.dev/post/15491543

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?

#linux

threaded - newest

bjoern_tantau@swg-empire.de on 13 Jun 23:32 next collapse

Maybe use a graphical file manager?

Or move the folder to /tmp or so.

friend_of_satan@lemmy.world on 14 Jun 00:02 next collapse

Or a tui file manager like ncdu

Buttons@programming.dev on 14 Jun 00:29 collapse

That’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 -rf and 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 /tmp is a nice suggestion that can work on anywhere without special programs or scripts.

SpaceNoodle@lemmy.world on 14 Jun 02:03 next collapse

You don’t sound like you’re comfortable with the command line.

Buttons@programming.dev on 14 Jun 10:38 collapse

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 -rf in 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 a rm -rf command has caused me needless hours of work in the past.

I realized the main reason I have to use rm -rf is 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.

t_378@lemmy.one on 14 Jun 16:35 collapse

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’.

somethingsomethingidk@lemmy.world on 14 Jun 02:08 collapse

If you’re making backups of things you care about and not running sudo rm -rf the 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.

redbr64@lemmy.world on 14 Jun 02:33 collapse

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

wildbus8979@sh.itjust.works on 13 Jun 23:35 next collapse

chmod -R the directory first?

ryannathans@aussie.zone on 14 Jun 02:07 collapse

This, lol just remove write protection if -f is too spooky

nottelling@lemmy.world on 13 Jun 23:36 next collapse

So… you’re afraid of the command that does the thing you’re trying to do?

Buttons@programming.dev on 14 Jun 00:21 collapse

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 .git directory, what it does is ignore all prompts for all files.

saigot@lemmy.ca on 14 Jun 00:53 next collapse

so why not rm -rf folder/.git/* then rm -r folder/*

fhein@lemmy.world on 14 Jun 08:23 collapse

Maybe they’re afraid of accidentally writing rm -rf folder/.git /* or something

Buttons@programming.dev on 14 Jun 10:39 next collapse

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.

IsoKiero@sopuli.xyz on 14 Jun 11:04 next collapse

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] on 14 Jun 21:09 next collapse

.

OneCardboardBox@lemmy.sdf.org on 15 Jun 00:13 next collapse

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.

intensely_human@lemm.ee on 15 Jun 11:59 collapse

Are you regularly deleting git repos?

racketlauncher831@lemmy.ml on 15 Jun 09:11 collapse

Generally that is not a concern because regular users won’t be able to rm anything 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.

fhein@lemmy.world on 16 Jun 08:56 collapse

If someone is careless, they should create a wrapper around rm, or just use a FM.

I think that’s the situation OP is in… They don’t trust themself with these kinds of commands, while other commenters here are trying to convince them that they should just use rm -rf anyway

Yearly1845@reddthat.com on 14 Jun 02:33 next collapse

You just need to do this then

cd git-project
rm -rf .git
cd ..
rm -r git-project

With 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.

gamma@programming.dev on 20 Jun 18:01 collapse

What about adding the flags last?

rm deletethisrepo -rf
davel@lemmy.ml on 13 Jun 23:39 next collapse

I’ve shot myself in the foot enough times over the years with rm -rf. Now I use trash-cli. I don’t know what package manager(s) you use, but I install it via Homebrew.

treadful@lemmy.zip on 13 Jun 23:49 next collapse

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 sudo for user files.

friend_of_satan@lemmy.world on 14 Jun 00:00 next collapse

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 -fv

This will print out all the rm -fv commands that would be run. It’s basically rm -rf --dry-run, but rm doesn’t have that common option. Once you’ve verified that that’s what you want to do, run it again without echo to 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 echo pattern a lot when I’m crafting commands that are potentially destructive or change lots of things.

potatopotato@sh.itjust.works on 14 Jun 02:32 next collapse

github.com/nivekuil/rip This is what you’re looking for

bloodfart@lemmy.ml on 14 Jun 03:21 next collapse

Cd into the directory first, then run rm -rf, then cd back out and rm -r just the directory.

E:fb

etchinghillside@reddthat.com on 14 Jun 03:40 next collapse

OSX - mv my_project ~/.Trash

eldavi@lemmy.ml on 14 Jun 04:09 next collapse

git rebase doesn’t work?

intensely_human@lemm.ee on 15 Jun 12:03 collapse

That or an oil change

Kekin@lemy.lol on 14 Jun 04:36 next collapse

A tip I saw some time ago is to do:

rm folder -rf

Additionally you could move the git folder to the trash folder. I think it’s usually located at $HOME/.local/share/trash/files/

Then you can delete it from the trash once you’re certain you got the right folder

d_k_bo@feddit.de on 14 Jun 12:41 collapse

Additionally you could move the git folder to the trash folder. I think it’s usually located at $HOME/.local/share/trash/files/

Moving something to the trash files folder isn’t the correct way to trash it, since the Trash specification requires storing some metadata for each trash item.

You should use eg. trash-cli instead.

boredsquirrel@slrpnk.net on 14 Jun 13:15 collapse

xdg-trash

gomp@lemmy.ml on 14 Jun 07:00 next collapse

The problem is that rm -rf shouldn’t scare you?

What are the chances something like

~/projects/some-project $ cd ..
~/projects $ rm -fr some-project

may delete unexpected stuff? (especially if you get into the habit of tab-completing the directory argument)

WarmApplePieShrek@lemmy.dbzer0.com on 14 Jun 19:07 next collapse

Use rm -rf. If you are scared of mistakes, type echo rm -rf nameofdirectory, check it, go back, delete the echo and press enter.

biribiri11@lemmy.ml on 14 Jun 23:36 next collapse

If you’re nervous about rm, there’s many alternatives that work by moving a file to your recycling bin instead of deleting it outright. I think the current fun one is trash-rs, but some distros package trash-cli.

flux@lemmy.ml on 14 Jun 23:52 next collapse

You should have backups. Preferably also snapshots. Then rm will feel less scary.

krnl386@lemmy.ca on 14 Jun 23:58 next collapse

If you’re that worried, why not run chmod -R u+w .git inside the project dir to “un write-protect” the files, then just ascend to the directory containing the project dir (cd …) and use rm -r without -f?

The force flag (-f) is the scary one, I presume?

mactan@lemmy.ml on 15 Jun 03:57 next collapse

its a bit verbose but my preference is rm -r --interactive=never directoryname

i really try to avoid rf for myself

[deleted] on 15 Jun 04:15 next collapse

.

iopq@lemmy.world on 15 Jun 09:44 collapse

Ah, yes, run a bash file executing rm -rf $1

What could go wrong?

nigh7y@lemmy.ml on 15 Jun 15:06 collapse

Sure. Solution removed.

BaumGeist@lemmy.ml on 15 Jun 04:59 next collapse

chmod -R 777 my_project_managed_by_git && rm -r my_project_managed_by_git

qaz@lemmy.world on 15 Jun 10:43 next collapse

You can use ls <PATH> first to check you are deleting the right files. I do this and I’ve never accidentally deleted the wrong files (using rm).

Pika@sh.itjust.works on 15 Jun 19:32 next collapse

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

ssm@lemmy.sdf.org on 15 Jun 20:01 collapse

use relative paths (cd into the directory below your repository) and use tab completion, and you won’t have problems.