Geek asks and answers

Git stops resolving files renamed after reaching a certain number of added / deleted files

I have a large ant project, versioned in Git. We are currently changing the construction tool to maven. This means moving all java source files to a different directory structure. I created a bash script to move java sources to one directory tree and other resources to another directory. wood. I convert one module (source code) after another.

I run git statusafter moving each module, and first I see the correct status RENAMEDwith each file.

After moving another module and the number of moved files reaches about 100 , git stops recognizing the moved files and separates them. This means that after starting, git statusI see every file (event correctly recognized before) twice. One DELETEDin the old way and one NEW FILEin the new way.

Is there something that limits the number of files automatically resolved when renaming?

+5
source share
1 answer

What do you value

diff.renameLimit

?

Try to install

git config diff.renameLimit 0

to disable the restriction or try to set a very high value.

+4
source

More articles:


All Articles