title: Git: Never Commit Changed Files (But still keep original revisioned.)
body: <p>What is a good <em>git</em> practice to denote that a changed file should never be committed?</p>
  
  <p>For example, for a WordPress theme development project, I am tracking the original WordPress files in <em>git</em>; and the <em>wp-config.php</em> config file, which contains local info that only pertains to the current system, needs to be changed but I don't want to commit it to <em>git</em>.</p>
  
  <p>In Perforce, I used to save this type of event as a <em><a href="http://www.perforce.com/perforce/doc.current/manuals/p4guide/04_files.html" rel="nofollow noreferrer">numbered changelist</a></em> and never check it in. I was wondering whether a similar trick is available with <em>git</em>.</p>