title: Who touched my git assume-unchanged bit?
body: <p>I have a certain file in my repo that I have set the assume unchanged bit on:</p>
  
  <pre><code>git update-index --assume-unchanged someFile.txt
  </code></pre>
  
  <p>Once in a while, after some work on the repo, that bit is unset and the file is automagically not <code>assume-unchanged</code> anymore.</p>
  
  <p>Who's touching it? How can I make this permanent until I explicitly tell git to:</p>
  
  <pre><code>git update-index --no-assume-unchanged someFile.txt
  </code></pre>
  
  <p>What's going on here?</p>
  
  <hr>
  
  <p><strong>Edit</strong>: I'm using the assume-unchanged bit on configuration files that change locally, and should never ever be committed, not to mention pushed upstream. I don't want to see them in <code>git status</code>, nor anywhere else, unless I explicitly tell git I want to edit and commit one of them.</p>
  
  <hr>
  
  <p><strong>Edit</strong>: OK, I think I managed to reproduce the issue.</p>
  
  <p>I committed the file from a different repo (which didn't have it as <code>--assume-unchanged</code>), pulled on my repo, and sure enough, the bit was reset.</p>
  
  <p>So two questions arise:</p>
  
  <ol>
  <li>Is it possible to set this bit on the central authoritative repo so that it propagates to all repos?</li>
  <li>Is it possible to make this bit sticky, even after remote changes to it?</li>
  </ol>