It makes using the Source Control module harder and less intuitive, because if you close a repository, there is no obvious way to reopen it and VSCode just stops recognizing it. I do not agree with "Manually cl
NOT when disabling in a sub workspace folder (noop) Prettier 1.10, vue jsonc postcss support.[1.0.0]Prettier 1.9 New option: requireConfig (boolean) Format only files which have a prettier config (.prettierrc, ...) Don't merge editor's options into prettier config...
but I noticed that if you were to map a network share to a drive in Windows, and specify a network drive location, Git will let you add that as a safe directory, but it seems
Error: The folder ".git" is not a Git repository, and therefore could not be added to Git Graph. What does the bug relate to Recognizing git repo To reproduce F1 Git Graph: Add git repository select .git folder Expected behaviour Recognise git repo Environment Windows 10 Visual Studio Code...
I have triedgit config --global core.ignorecase true, but that too did not help. This not only needs to be fixed from a repository end, I believe this should be fixed in VSCode too, where Windows ignores case and does a merge on the folder and thus, git losing all the tracking. ...
@Esger<https://github.com/Esger>, sorry for not getting back to you on this until now. Can you please confirm that you are unable to initialise a repository using the following steps: - Create a new folder foo - In terminal navigate inside the foo folder and type code-insiders . - ...
I think I've found where the issue is (at least for iOS 10.2.1) - it looks like the app is responding a bit different to GDB commands we're using to launch it and we're not recognizing that response. I'll send a PR shortly. @JKeetman, as for your problem, this is a known ...