fatal: not a git repository (or any of the parent directories): .git

Git’s fatal: not a git repository (or any of the parent directories): .git error means you ran a Git command in a directory that isn’t tracked by Git and has no .git folder in any parent folder.

What It Means

Every Git repository has a hidden .git/ directory that stores version history, configuration, and metadata. When you run a Git command like git status, git add, or git commit, Git looks for this .git/ folder — first in the current directory, then in each parent directory. If it can’t find one, it stops with this error.

Why It Happens

• You haven’t initialized Git in the project yet with git init.
• You cloned a repo but cd’d into a subdirectory that isn’t part of the repo (unlikely, but possible with misconfigured submodules).
• The .git/ folder was deleted or corrupted.
• You’re running Git commands from outside the project entirely (e.g., your home directory or /tmp).

How to Fix It

1. Check if you’re inside a Git repo

Run this to confirm the error:

git rev-parse --git-dir

If you see the error, you’re outside a Git repo, or the repo isn’t initialized.

2. Initialize a new Git repo (if starting fresh)

git init

This creates a .git/ directory in the current folder. Now git status, git add, and other commands will work.

3. Clone an existing repo instead

If you meant to work on an existing project, clone it:

git clone https://github.com/user/repo.git
cd repo

4. Navigate to the correct directory

If the repo exists somewhere else on your machine:

ls -la              # look for a .git folder
cd /path/to/repo   # navigate to the actual repo

5. Restore a deleted .git/ folder

If .git/ was accidentally deleted, you can’t fully recover the history without a remote. If a remote exists, clone the repo again:

git clone https://github.com/user/repo.git

If there’s no remote but you have the working files, initialize a new repo and add them:

git init
git add .
git commit -m "Initial commit"