git assume-unchanged implications

Say I have a file which is tracked by git and at some point I want my local repository to ignore the changes I make to this file. This is, if I understand correctly, the case to use (link1;link2)

git update-index --assume-unchanged

My question is, what happens with this file in case there are changes on a remote repository? Will the changes be reflected in my local copy?

  • Difference between prunings in git
  • git How to merge a branch into the master branch by completely overwriting master branch
  • Why can't I use TortoiseMerge as my git merge tool on Windows?
  • Creating Git branch tag in VSO or VS2015
  • git-upload-pack not found
  • One project, Multiple customers with git?
  • This answer suggests the same solution – but the comment which address my question was left unanswered…

  • Git LFS always shows image files as changed?
  • How to merge many commits into one in github repository
  • Is it possible to accept user input as part of a remote git post-receive hook?
  • why do I have to hit q at the end of git log
  • Difference between ** and * in glob matching (.gitignore)
  • Moving a git repository down a hierarchy level
  • One Solution collect form web for “git assume-unchanged implications”

    The “assume-unchanged” bit is stored in your index, not in the repository itself. Thus fetch/pull/push do not propagate that setting to or from other repositories, which means it is a local setting. Users of other clones of the repository may very well create new commits involving that file. I’m not sure there’s a “simple” answer regarding how to deal with this scenario, as it depends on what exactly you’re trying to do, and what is being done in other repositories.

    Git Baby is a git and github fan, let's start git clone.