threads / discuss / 55813

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

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

## tl;dr

2 messages between Jun 1, 2021 and Jun 1, 2021.

replies: 1people: 2as markdown or json

AndyAo· Jun 1, 2021, 00:26 UTC · lore

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· Jun 1, 2021, 01:33 UTC · re: AndyAo · lore

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

AndyAo <zen96285@gmail.com> writes:
Show 7 quoted lines
> 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).

← back to recent threads