54

I cloned a git repository but accidentally messed up. So I re-cloned and the message showed up:

destination path already exists and is not an empty directory

I've tried deleting folders in my mac with the name of the destination path but it did not work.

I'm very new to coding so all help would be appreciated.

RBT
  • 21,293
  • 19
  • 144
  • 210
flopga slays
  • 567
  • 1
  • 4
  • 3
  • what error message you got ? –  May 16 '18 at 01:15
  • fatal: destination path 'XXX' already exists and is not an empty directory – flopga slays May 16 '18 at 01:19
  • 4
    why don't you simply `rm -rf XXX` ? – Gilles Gouaillardet May 16 '18 at 01:38
  • 1
    Possible duplicate of [Fatal: destination path 'opencv\_contrib' already exists and is not an empty directory](https://stackoverflow.com/questions/42686465/fatal-destination-path-opencv-contrib-already-exists-and-is-not-an-empty-dire) – phd May 16 '18 at 11:36
  • Related: [How to get Git to clone into current directory](https://stackoverflow.com/questions/9864728/how-to-get-git-to-clone-into-current-directory) – krubo Oct 04 '19 at 18:21
  • Either delete the current folder or rename it and get a clone – VishalParkash May 28 '20 at 12:01
  • this is a pretty straightforward git question, but has no duplicated flag nor accepted answer after two years – Daemon Painter Aug 06 '20 at 21:31
  • I had this issue because I didn't spot that the directory had a hidden file in (configuration file of my IDE). I moved the file out, did the clone and then put it back. – wkille Mar 05 '21 at 09:46
  • I think the proper answer to this question would be if there is an option on git to **force** clone a repo, even into a non-empty directory. There is no real reason why this shouldn't be possible; at worst you may want to forbid cloning into a directory that already has a `.git` file. However, it doesn't seem to be possible (or no one here knows how). – Marses Jun 24 '21 at 17:15
  • Gilles got the right answer. You need to remove that invisible folder with a suffix .git. To see that folder, use ls -a. To remove it, use rm -rf – Chen Lizi Jul 14 '21 at 16:09

11 Answers11

18

This error comes up when you try to clone a repository in a folder which still contains .git folder (Hidden folder).

If the earlier answers doesn't work then you can proceed with my answer. Hope it will solve your issue.

Open terminal & change the directory to the destination folder (where you want to clone).

Now type: ls -a

You may see a folder named .git.

You have to remove that folder by the following command: rm -rf .git

Now you are ready to clone your project.

Farid Chowdhury
  • 2,011
  • 20
  • 18
  • 2
    It also comes up when there is no `.git` folder however. For example, if you make a project folder with PyCharm, you will have an `.idea` folder. I think what OP needs is a way to "force" git to clone the repo, overwrite or not (although in the above situation overwriting wouldn't even be required). – Marses Jun 24 '21 at 17:14
17

Explanation

This is pretty vague but I'll do what I can to help.

First, while it may seem daunting at first, I suggest you learn how to do things from the command line (called terminal on OSX). This is a great way to make sure you're putting things where you really want to.

You should definitely google 'unix commands' to learn more, but here are a few important commands to help in this situation:

ls - list all files and directories (folders) in current directory

cd <input directory here without these brackets> - change directory, or change the folder you're looking in

mkdir <input directory name without brackets> - Makes a new directory (be careful, you will have to cd into the directory after you make it)

rm -r <input directory name without brackets> - Removes a directory and everything inside it

git clone <link to repo without brackets> - Clones the repository into the directory you are currently browsing.

Answer

So, on my computer, I would run the following commands to create a directory (folder) called projects within my documents folder and clone a repo there.

  1. Open terminal
  2. cd documents (Not case sensitive on mac)
  3. mkdir projects
  4. cd projects
  5. git clone https://github.com/seanbecker15/wherecanifindit.git
  6. cd wherecanifindit (if I want to go into the directory)

p.s. wherecanifindit is just the name of my git repository, not a command!

Sean Becker
  • 471
  • 1
  • 5
  • 6
  • 1
    And if I were to receive the error you're getting, I would go into the projects directory and run `rm -rf wherecanifindit`, like the other people said. `rm` removes a file, `rm -r` removes a directory, and `rm -f` stops the command line from asking you questions. Put that all together and you get `rm -rf` – Sean Becker May 16 '18 at 01:46
5

Steps to get this error ;

  1. Clone a repo (for eg take name as xyz)in a folder
  2. Not try to clone again in the same folder . Even after deleting the folder manually this error will come since deleting folder doesn't delete git info .

Solution : rm -rf "name of repo folder which in out case is xyz" . So

rm -rf xyz
ArpitA
  • 683
  • 6
  • 16
4

This just means that the git clone copied the files down from github and placed them into a folder. If you try to do it again it will not let you because it can't clone into a folder that has files into it. So if you think the git clone did not complete properly, just delete the folder and do the git clone again. The clone creates a folder the same name as the git repo.

James Knott
  • 1,052
  • 6
  • 6
3

What works for me is that, I created a new folder that doesn't contain any other files, and selected that new folder I created and put the clone there.

I hope this helps

Neuron - Freedom for Ukraine
  • 4,303
  • 4
  • 29
  • 51
belards
  • 31
  • 1
  • Hello, and welcome to SO. Very much like [James Knott's answer](https://stackoverflow.com/a/50361155/2125110) the solution is indeed to clone the repository elsewhere. – Daemon Painter Aug 06 '20 at 21:37
2

Make a new-directory and then use the git clone url

Varun Kumar
  • 123
  • 10
2

For those comming here wishing to clone a repo in an existing folder that already contains files/folders, try this:

cd /
git init
git remote add origin <your-repo>
git pull
git checkout master -f

This example is for the root folder. Change "/" to point to your specific folder

Rafa Alonso
  • 29
  • 1
1

If you got Destination path XXX already exists means the name of the project repository which you are trying to clone is already there in that current directory. So please cross-check and delete any existing one and try to clone it again

1

I got same issue while using cygwin to install nvm

In fact, the target directory where empty but the git binary used was the one from windows (and not git from cygwin git package).

After installing cygwin git package, the git clone from nvm install was ok!

boly38
  • 1,697
  • 21
  • 29
  • The issue at hand is trying to clone a repository in a location which is already a git repository. This answer doesn't help with that. – Daemon Painter Aug 06 '20 at 21:36
  • 1
    @DaemonPainter your comment is often true in many cases, but I don't undertstand why you down vote for the rest. A solution to a given issue is not always one an only one answer, because it's depends of your context. Your action helps nobody. – boly38 Aug 07 '20 at 06:39
0

An engineered way to solve this if you already have files you need to push to Github/Server:

  1. In Github/Server where your repo will live:

    • Create empty Git Repo (Save <YourPathAndRepoName>)
    • $git init --bare

  2. Local Computer (Just put in any folder):

    • $touch .gitignore
    • (Add files you want to ignore in text editor to .gitignore)

    • $git clone <YourPathAndRepoName>

    • (This will create an empty folder with your Repo Name from Github/Server)

    • (Legitimately copy and paste all your files from wherever and paste them into this empty Repo)

    • $git add . && git commit -m "First Commit"

    • $git push origin master
kevin_theinfinityfund
  • 1,043
  • 11
  • 13
  • He needs to clone, but is trying to clone into a location that is already a git repository. This answer doesn't help with that. – Daemon Painter Aug 06 '20 at 21:35
  • 1
    @DaemonPainter the question states that they've tried deleting the folders; thus, it's presumed that they are trying to restart after an `rm -f path` but they still have files they want to commit to an initially empty git repo. – kevin_theinfinityfund Aug 07 '20 at 18:15
  • True, but the comment posted under [this answer](https://stackoverflow.com/a/50361155/2125110) by the asker states "I'm an idiot, I didn't delete it properly". To me, it looks like the asker is admitting the proposed solution is to _not_ attempt to clone into an existing repo... – Daemon Painter Aug 07 '20 at 19:04
-3

Use Command: ls -a You will see list of files or folders that's blocking it. Use Command : rm -r Foldername/filename

After deleting all the files and folders. You can clone your project to the directory

Rotimi Ayobami
  • 15
  • 3