-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Git merge conflicts not showing #112713
Comments
(Experimental duplicate detection) |
@souvikbiswas1998 can you give more symptom information? Yesterday when I had to merge, when I clicked on the blue highlight 'merge conflict' files, it wouldn't open them, but because they're highlighted I could switch from Source Control tab to Project Files tab, and could then select the file from there. Files that were irregular (I had 10 png's and 8 ttf fonts) didn't want to open at all until the merge was complete. My side it could be to do with the bug of VS Code not letting go of files after closing, but that doesn't explain Merge Conflict files not being open-able. |
mainThreadExtensionService.ts:65 [[object Object]]Should never happen |
This is the snapshot of the problem. the conflicts files are mentioned below: |
Temporary solution here: Corresponding Git blame: |
The Even though we’re only trying to access the |
Duplicate of #112537 (which will be fixed in tomorrow's insiders) |
@eamodio that's epic, thanks for cleaning up. |
Issue Type: ### Bug
SCM panel not showing the conflict files.
The text was updated successfully, but these errors were encountered: