New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revealing settings or keybinding files in explorer #91534
Comments
@aeschli Can we enable this to the resource scheme - |
This bug has been fixed in to the latest release of VS Code Insiders! @Jupakabra, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text Happy Coding! |
@meganrogge you can reopen issues when you add verification-found |
@sandy081 thanks a lot for investigating and for bisecting! |
@JacksonKearl the bot is bullying me here :D |
\closedWith 8f410da |
This bug has been fixed in to the latest release of VS Code Insiders! @Jupakabra, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text Happy Coding! |
@isidorn looking at the timeline I can't figure out why it was repeatedly commenting... it's expected to comment if |
Version: 1.43.0-insider
Commit: b0be067
OS: Windows_NT x64 10.0.17763
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
Was this purposely removed for settings? Because it used to work before and now there is no way to get to settings files for backup or copy purposes.
The text was updated successfully, but these errors were encountered: