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?

  • Remove a specific commit but keep all the commits afterward
  • use hub, the github-gem or just stick to git when working with github repo's?
  • Difference between git bundle and .patch
  • Reinitialize Git Repo
  • What does the --stdlayout do in git svn clone?
  • Error finding tcl.init when running Git GUI
  • This answer suggests the same solution – but the comment which address my question was left unanswered…

  • How to add image to readme file in Stash
  • git with development, staging and production branches
  • Ignore specific commit but stay in head
  • How to save the current state of my staging area?
  • Git apply patch fails silently (no errors but nothing happens)
  • Why “git fetch origin branch:branch” works only on a non-current branch?
  • 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.