“fatal: Not a git repository (or any of the parent directories)” from git status

This command works to get the files and compile them:

git clone a-valid-git-url

for example:

  • bundle install leads to git clone error. Not sure what this response means
  • git clone: RPC failed; result=22; HTTP code = 408
  • git clone from bitbucket.org is not working by https
  • Git clone hangs in Windows bash
  • how to ignore .gitignore action when cloning?
  • Chosen plugin Options are not passed to Cloned row
  • git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghts
    

    However, git status (or any other git command) then gives the above fatal: Not a git repository (or any of the parent directories) error.

    What am I doing wrong?

  • Setting a password for Git cloning?
  • Getting the information of squashed commits in Git
  • managing two forks/branches in github
  • How do I get the list of files about to be updated by `git pull` without knowing the branch name or what it tracks?
  • vimdiff between current and previous git version of a file
  • Not able to import git android project in Eclipse
  • 9 Solutions collect form web for ““fatal: Not a git repository (or any of the parent directories)” from git status”

    You have to actually cd into the directory first:

    $ git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghts
    Cloning into 'liggghts'...
    remote: Counting objects: 3005, done.
    remote: Compressing objects: 100% (2141/2141), done.
    remote: Total 3005 (delta 1052), reused 2714 (delta 827)
    Receiving objects: 100% (3005/3005), 23.80 MiB | 2.22 MiB/s, done.
    Resolving deltas: 100% (1052/1052), done.
    
    $ git status
    fatal: Not a git repository (or any of the parent directories): .git
    $ cd liggghts/
    $ git status
    # On branch master
    nothing to commit (working directory clean)
    

    In my case, was an environment variable GIT_DIR, which I added to access faster.

    This also broke all my local repos in SourceTree 🙁

    in my case, i had the same problem while i try any git — commands (eg git status) using windows cmd. so what i do is after installing git for window https://windows.github.com/
    in the environmental variables, add the class path of the git on the “PATH” varaiable. usually the git will installed on C:/user/"username"/appdata/local/git/bin add this on the PATH in the environmental variable

    and one more thing on the cmd go to your git repository or cd to where your clone are on your window usually they will be stored on the documents under github

    cd Document/Github/yourproject
    

    after that you can have any git commands

    I had another problem. I was in a git directory, but got there through a symlink. I had to go into the directory directly (i.e. not through the symlink) then it worked fine.

    Sometimes its because of ssh. So you can use this:

    git clone https://cfdem.git.sourceforge.net/gitroot/cfdem/liggghts
    

    instead of:

    git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghts
    

    I just got this message and there is a very simple answer before trying the others. At the parent directory, type git init

    This will initialize the directory for git. Then git add and git commit should work.

    Simply, after you clone the repo you need to cd (change your current directory) to the new cloned folder

    git clone https://User_Name@bitbucket.org/Repo_Name.git
    
    cd Repo_Name
    

    In my case, the original repository was a bare one.

    So, I had to type (in windows):

    mkdir   dest
    cd dest
    git init
    git remote add origin a\valid\yet\bare\repository
    git pull origin master
    

    To check if a repository is a bare one:

    git rev-parse --is-bare-repository 
    

    git clone https://github.com/klevamane/projone.git
    Cloning into ‘projone’…
    remote: Counting objects: 81, done.
    remote: Compressing objects: 100% (66/66), done.
    remote: Total 81 (delta 13), reused 78 (delta 13), pack-reused 0
    Unpacking objects: 100% (81/81), done.

    you have to “cd projone”
    then you can check status.


    One reason why this was difficult to notice at first, i because you created a folder with the same name already in your computer and that was where you cloned the project into, so you have to change directory again


    Git Baby is a git and github fan, let's start git clone.