nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Removing a repository removes all files in folder

timbellomo

This may be completely obvious to people with more git experience, but while removing a repository that I created in error (without even the initial commit having been done), I caused the deletion of all of the contents of the folder in which the repository was created.

Perhaps this is how git is intended to work, but it's not what I expected. My naiviety led me to believe that removing the repository would simply delete any versioned changes, leaving on disk the current "working copy" of the individual files.

Is this how removing a repository (not just a bookmark) is supposed to work? Should it have deleted all files in that same directory (even though they hadn't been committed to the repo yet)?

*edited title for clarity

Accepted answers

stevestreeting

When you remove a bookmark, you are given 2 choices - just remove the bookmark, or remove the bookmark AND delete the repository on disk. The default option is to simply remove the bookmark, not to delete anything on disk. Here's a screenshot of the Windows version for example, but the behaviour is the same on Mac: http://screencast.com/t/Do6UoAdfpOy8

All comments

stevestreeting

timbellomo

Right -- I chose the latter, because I actually wanted to delete the newly-created-in-error repo.

Consider the following:

I'm working on myfantasicproject for several weeks. I've got a decent chunk of files and folders that I've been working with. I suddenly realize, "Shame on me! I should be using git!" I go into SourceTree, and create a new repository in the top-level directory of my project. Yay!

Before continuing, though, I realize that, well, maybe it would be better if I managed some of these pieces in separate repositories, say one for the client, and one for the server, and not just one monolithic repo for the whole folder. So I want to remove the repo, and create my two smaller ones. When prompted, I say, "yeah, don't just remove the bookmark from SourceTree; actually just delete that repo -- I made it in error; it doesn't even really contain anything (I haven't committed anything)." Boom goes the directory.

I'm not asserting that they're should be any changes made, just giving some feedback on my confusion. If you decide that it's clear and doesn't need any changes, I respect that. As I said, I'm a git beginner, so perhaps the terminology isn't as familiar to me as it should be.

Thanks for your consideration.

timbellomo

Right -- I chose the latter, because I actually wanted to delete the newly-created-in-error repo.

Consider the following:

Thanks for your consideration.

stevestreeting

Ah, I see - I didn't appreciate you'd interpreted it as just referring to the .git folder rather than the source folder. Perhaps this can make this clearer in the message.

stevestreeting

I've added a new secondary warning dialog (Windows version right now), which only occurs when the repo you've asked to delete has uncommitted changes (modified files or untracked files). Hope that helps avoid this misunderstanding in future.

New dialog

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree