# How to disable Git from automatically identifying and managing embedded git repositories?

2 messages from 2021-06-01 to 2021-06-01. Participants: AndyAo, Junio C Hamano.
Thread: https://gitlist.dev/t/55813

## AndyAo, 2021-06-01 00:26

Subject: How to disable Git from automatically identifying and managing embedded git repositories?
Message-ID: <c4d32a7b-94c5-b613-ae5e-9c18b1ffa627@gmail.com>
URL: https://gitlist.dev/e/c4d32a7b-94c5-b613-ae5e-9c18b1ffa627%40gmail.com

```
When I upgraded Git from 2.24.1.windows.2 to 2.29.2.windows.2, I noticed 
that the embedded git repository is recognized in `git status`, and if I 
use `git add .` will manage the embedded git repository directly as a 
submodule, instead of just ignoring them, which is the behavior I want.

How do I turn this off?

Thanks.


```

## Junio C Hamano, 2021-06-01 01:33

Subject: Re: How to disable Git from automatically identifying and managing embedded git repositories?
Message-ID: <xmqqczt6v06h.fsf@gitster.g>
URL: https://gitlist.dev/e/xmqqczt6v06h.fsf%40gitster.g
In-Reply-To: <c4d32a7b-94c5-b613-ae5e-9c18b1ffa627@gmail.com>

```
AndyAo <zen96285@gmail.com> writes:

> When I upgraded Git from 2.24.1.windows.2 to 2.29.2.windows.2, I
> noticed that the embedded git repository is recognized in `git
> status`, and if I use `git add .` will manage the embedded git
> repository directly as a submodule, instead of just ignoring them,
> which is the behavior I want.
>
> How do I turn this off?

You can use the ignore mechanism to exclude it and "git add ." would
not touch it.

In my checkout of the git repository, I have a separate copy of the
same git repository and checked out at the path "Meta/".  In the
upper-level repository, I have "/Meta" in .git/info/exclude (among
other private-ignore patterns), and that would keep it out of the
main repository's index even with "git add ." (not that I'd ever use
"add everything", which I do not think have any place in my
workflow).  This is done without using .gitignore because it is
nobody else's business that I use such a "strange" setup and use the
pathname "Meta/" for it (hence project participants do not have to
know about it).

```
