-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
SCM panel doesn't show git conflicts list of files #112537
Comments
(Experimental duplicate detection)
|
possibly related to #112713 seeing the same, seems to be related to conflicts of type |
@fspoettel Same issue here. I think you're right with the type of conflict causing the issue. |
Temporary solution: Corresponding Git blame: |
fix microsoft#112537 and related issues
fix microsoft#112537 and related issues.
@joaomoreno You know more about these changes than me -- does the spirit of this PR look like the right direction? |
Sounds good, never thought about this case. |
This bug has been fixed in to the latest release of VS Code Insiders! @maltaesousa, 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! |
/verified |
How long will it take to fix this bug? |
They already fixed it (thanks to them) and it's already in master. You can download VS Code Insiders or wait until next release that probably will come out February 3rd. |
Issue Type: Bug
This bug happens on version: 1.51.2 and Insiders 1.53.0. Version 1.51.1 works fine.
In a project with git enabled:
Console errors:
VS Code version: Code - Insiders 1.53.0-insider (96b426e, 2020-12-14T05:59:27.649Z)
OS version: Windows_NT x64 10.0.17134
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: