Ignore changes in tracked files. stub

suggest change

.gitignore and .git/info/exclude work only for untracked files.

To set ignore flag on a tracked file, use the command update-index:

git update-index --skip-worktree myfile.c

To revert this, use:

git update-index --no-skip-worktree myfile.c

You can add this snippet to your global git config to have more convenient git hide, git unhide and git hidden commands:

    hide   = update-index --skip-worktree
    unhide = update-index --no-skip-worktree
    hidden  = "!git ls-files -v | grep ^[hsS] | cut -c 3-"

You can also use the option –assume-unchanged with the update-index function

git update-index --assume-unchanged <file>

If you want to watch this file again for the changes, use

git update-index --no-assume-unchanged <file>

When --assume-unchanged flag is specified, the user promises not to change the file and allows Git to assume that the working tree file matches what is recorded in the index.Git will fail in case it needs to modify this file in the index e.g. when merging in a commit; thus, in case the assumed-untracked file is changed upstream, you will need to handle the situation manually.The focus lies on performance in this case.

While --skip-worktree flag is useful when you instruct git not to touch a specific file ever because the file is going to be changed locally and you don’t want to accidentally commit the changes (i.e configuration/properties file configured for a particular environment). Skip-worktree takes precedence over assume-unchanged when both are set.

Feedback about page:

Optional: your email if you want me to get back to you:

Table Of Contents