What does "fatal: not a git repository" mean?

This error means Git cannot find a .git directory in your current folder or any of its parent folders. The .git directory is what makes a folder a Git repository. Without it, Git commands have no repository to operate on.

How do I check if I am inside a Git repository?

Run "git rev-parse --is-inside-work-tree" in your terminal. If it prints "true", you are inside a Git repository. If it returns the "fatal: not a git repository" error, you are not. You can also check if a .git folder exists by running "ls -la" and looking for it.

I accidentally deleted my .git folder. Can I recover it?

If you deleted .git locally but the repository exists on a remote (GitHub, GitLab, etc.), you can recover by cloning it again with "git clone". If there is no remote copy, the history is lost permanently. Your source files are still intact, but all commits, branches, and tags are gone. This is why pushing to a remote regularly is important.

Why do I get this error in VS Code or my IDE?

Your IDE likely opened a parent folder that is not a Git repository, or opened a subfolder instead of the project root. Make sure you open the folder that contains the .git directory. In VS Code, use File > Open Folder and select the correct project root.

Can I get this error inside a subdirectory of a Git repo?

No. Git automatically searches upward through parent directories until it finds a .git folder. If you are anywhere inside a Git repository, even deeply nested, Git will find it. This error only occurs when no .git folder exists in any parent directory all the way up to the filesystem root.

fatal: not a git repository How to fix this Git error

This is the most common Git error. It means Git cannot find a .git folder in your current directory or any parent directory. Here is how to diagnose and fix it in seconds.

Learn Git step by step Git Glossary

gitquest — enquête

Error explained

What this error means

When you see fatal: not a git repository (or any of the parent directories): .git, Git is telling you it looked for a .git/ folder in your current directory and every parent directory above it, but found nothing.

The .git/ folder is the hidden directory that stores your entire repository: commits, branches, configuration, and history. Without it, Git has no repository to work with and every Git command will fail.

This error does not affect your source files. Your code is safe. You just need to tell Git where the repository is, or create one.

gitquest — error

# You run a Git command and see this error

$git status

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

# Git cannot find a .git folder anywhere above your current location

Why it happens

Most common

Wrong directory

You opened a terminal or IDE in a folder that is not your project root. Maybe you are in your home directory, the Desktop, or a parent folder that does not contain a .git/ directory. This is by far the most frequent cause.

Easy to miss

Repository not yet created

You created a new project folder but forgot to run git init or git clone. The folder exists but it is not a Git repository yet. Git needs to be explicitly initialized before it can track changes.

Rare but serious

The .git folder was deleted

Someone (or a script) accidentally deleted the .git/ folder. This removes all version history from the local machine. If the project exists on a remote like GitHub, you can recover by cloning again. Otherwise the history is lost.

How to fix it

Three solutions depending on your situation. Start with the first one, which fixes the problem in most cases.

Navigate to the right folder

gitquest — fix cd

# Fix 1: Navigate to the correct project directory

$pwd

/home/user

$cd ~/projects/my-app

$git status

On branch main

nothing to commit, working tree clean

Initialize a new repository

gitquest — fix init

# Fix 2: Initialize a new repository here

$git init

Initialized empty Git repository in /home/user/my-project/.git/

$git status

On branch main

No commits yet

Clone from remote

gitquest — fix clone

# Fix 3: Clone the repository from remote

$git clone https://github.com/user/my-project.git

Cloning into 'my-project'...

remote: Enumerating objects: 42, done.

Receiving objects: 100% (42/42), done.

$cd my-project && git status

On branch main

How to prevent it

Always open the project root in your IDE

In VS Code, use File > Open Folder and select the directory that contains the .git/ folder. Opening a parent or sibling folder will cause this error in the integrated terminal.

Check your directory before running Git

Make a habit of running pwd before any Git command in a new terminal session. This takes one second and prevents confusion, especially when you have multiple projects open.

Push to a remote regularly

If your .git/ folder is ever accidentally deleted, having a remote backup on GitHub or GitLab means you can always recover the full repository with git clone.

Related commands

git init

Initialize a new Git repository from scratch

git clone

Clone an existing repository from a remote URL

git status

Check the current state of your repository

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

Questions about this error

Never get stuck on a Git error again

GitQuest teaches you Git through hands-on practice. Understand every command, every error, every fix.

Start learning Git