Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Recursive git update-index --assume-unchanged

Tags:

git

gitignore

I'm trying to run the following:

git update-index --assume-unchanged myFolderToIgnore 

Where myFolderToIgnore is a folder. However it fails saying its "unable to mark" it.

So I tried:

git update-index --assume-unchanged myFolderToIgnore/ 

Which GIT responds to with Ignoring path myFolderToIgnore/ but doesn't do anything (it still sees my changes and tries to check them in).

In the end I had to go in and manually mark each individual file as unchanged. What am I missing here?

like image 907
GxXc Avatar asked May 02 '13 19:05

GxXc


People also ask

How to Git assume unchanged?

In order to set "assume unchanged" bit, use --assume-unchanged option. To unset, use --no-assume-unchanged . To see which files have the "assume unchanged" bit set, use git ls-files -v (see git-ls-files[1]). The command looks at core.

What does Git update index do?

Overview. We use git update-index when we want to manually operate on files in Git staging area. This command supports two options that are often misused: –assume-unchanged and –skip-worktree. In this tutorial, we'll see how these two options differ and provide a use case for each.

What is Skip Worktree?

--skip-worktree explained: This allows you to make changes to a file that you don't want to be pushed to upstream. Use this option as already shown above.

What is refresh index in git?

git/index changed by windows. So it can only refresh the index and replace the . git/index file, which makes the next git status super fast and git status in windows very slow (because the windows system will refresh the index file again).


2 Answers

update-index is an internal plumbing command and thus not as comfortable as the real front-end commands. You will have to handle the recursion bit yourself:

git ls-files -z myFolderToIgnore/ | xargs -0 git update-index --assume-unchanged 

PSA: There is a high chance that assume-unchanged is not what you are looking for and you should use skip-worktree instead. See here for more info.

like image 109
Chronial Avatar answered Oct 13 '22 22:10

Chronial


I ran into this issue where my folder had hundreds of thousands of files, and thousands of folders.

This resulted in "Argument list too long".

The following solution will run the command for each folder and traverse the contents in those folders. So as long as your hundreds of thousands of files are separated in folders then this will work.

find . -maxdepth 1 -type d \( ! -name . \) -exec bash -c "cd '{}' && pwd && git ls-files -z ${pwd} | xargs -0 git update-index --assume-unchanged" \; 
like image 35
Chad Scira Avatar answered Oct 13 '22 21:10

Chad Scira