title: How enable/disable secret scanning in Azure/VSO
body: <p>in VSO, I have tried push the code without taking latest, when did that, my code got pushed locally. After pulling the latest code when i tried to push again to Central repository I am getting the below error.
  I had credentials in few files, after removing it also I'm getting the same error.
  Any help would be much appreciated, Thanks in Advance...!!!</p>
  <blockquote>
  <p>If these are valid credentials, even for non-production resources, you must remove them from Git’s branch history by resetting your branch or squashing all commits.
  See <a href="https://aka.ms/1escredscan" rel="nofollow noreferrer">https://aka.ms/1escredscan</a> for instructions. Please report any false positives to 1ESSecTools@microsoft.com.</p>
  </blockquote>
  <blockquote>
  <p>NOTE: It is not enough to remove the secrets and push another change. You must reset your branch according to the instructions.</p>
  </blockquote>
  <blockquote>
  <p>If this is a false positive, you can bypass credential scanning (for this push alone) by running these commands, assuming that you have no staged changes:</p>
  </blockquote>
  <pre class="lang-sh prettyprint-override"><code>git commit -m &quot;**DISABLE_SECRET_SCANNING**&quot; --allow-empty`
  git push
  </code></pre>
  <blockquote>
  <p>Alternatively, see <a href="https://aka.ms/1escredscan" rel="nofollow noreferrer">https://aka.ms/1escredscan</a> for instructions on how to use the hash values emitted above in a suppressions file to suppress false positives.)
  failed to push some refs to 'https://DevRepository'</p>
  </blockquote>
  <blockquote>
  <p>Error encountered while pushing to the remote repository: rejected Dev -&gt; Dev (VS403654: <strong>The push was rejected because it might contain credentials or other secrets.</strong></p>
  </blockquote>