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?

  • What are use cases for git namespaces?
  • How to fetch enough commits to do a merge in a shallow clone
  • Getting rid of temp-xxxx.rdb files
  • why my all index is change in my git project
  • How do I commit case-sensitive only filename changes in Git?
  • GIT Xcode - change origin
  • This answer suggests the same solution – but the comment which address my question was left unanswered…

  • remove all traces of a folder from git repo
  • How to show git differences like when performing a git pull?
  • Login is currently incompatible with git bash/cygwin
  • Does git clean support moving to Recycle Bin?
  • Merge conflict in a file that wasn't modified in either branch
  • Version Control for Graphics
  • 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.