<ul dir="auto">
<li>VSCode Version: 1.2.0</li>
<li>OS Version: Windows 8.1</li>
</ul>
<p dir="auto">Steps to Reproduce:</p>
<ol dir="auto">
<li>Open a repo in vscode so that the git bindings are active, leave this running in the background</li>
<li>Do your git interaction with TortoiseGit as usual</li>
<li>Notice that tortoise will regularly and randomly give errors failing to perform various operations because the repository appears to be locked (ie, some other git client is performing an operation). Tortoise will usually offer a 'retry' button; clicking retry almost always completes the action as intended.</li>
</ol>
<p dir="auto">I've noticed this seems to be related to whether I have vscode running or not. I suspect vscode is semi-actively doing fetches or something?<br>
I'm sure this is manually configurable, but I feel like it should be more intelligent than that... perhaps vscode may also silently be experiencing repo lock failures when I'm interacting with TortoiseGit, and perhaps vscode might take this as an indicator that I'm using a separate git client, and automatically (or offer to) reduce it's auto fetch behaviour?</p>
<p dir="auto">I'm not actually sure it's fetching, it could be something else, I just notice that the problems with TortoiseGit complaining about repo locks only seem to happen while vscode is running in the background.</p>
<p dir="auto">Several times now I've had mysteriously deleted files when doing a git pull in a console while Visual Studio Code is running. I've seen this roughly since version 0.10.</p>
<p dir="auto">It seems that when auto-merging, Git is able to delete a file but not able to write the merged file back if it's open in Code. However that is just a hypothesis.</p>
<p dir="auto">Seen the issue last with git version 1.9.5.msysgit.1 and Code 0.10.2.</p>