You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using VS Code with the Live Share extension enabled, I encountered an issue where the Git Gutter functionality does not seem to work as expected. The Git Gutter feature, which is supposed to display the Git diff information in the gutter of the code editor, is not functioning during Live Share sessions. This makes it challenging to track changes and quickly identify modified lines in collaborative coding sessions.
What was your system configuration? Product and Version: VS Code 1.80.1 OS Version: Windows 10 Live Share Extension Version: v1.0.5877 Target Platform or Language [e.g. Node.js]: Vue
Steps to Reproduce / Scenario:
Open Visual Studio Code.
Install and enable the Live Share extension.
Open a collaborative coding session with another participant using Live Share.
Make changes to the code in the shared session.
Observe that the Git Gutter markers, which should show changes in the code gutter (vertical column on the left), are not displayed during the Live Share session.
Please attach logs to this issue:
N/A
Screenshots
Left: Host
Right: Participant
The text was updated successfully, but these errors were encountered:
Describe what happened:
When using VS Code with the Live Share extension enabled, I encountered an issue where the Git Gutter functionality does not seem to work as expected. The Git Gutter feature, which is supposed to display the Git diff information in the gutter of the code editor, is not functioning during Live Share sessions. This makes it challenging to track changes and quickly identify modified lines in collaborative coding sessions.
What was your system configuration?
Product and Version: VS Code 1.80.1
OS Version: Windows 10
Live Share Extension Version: v1.0.5877
Target Platform or Language [e.g. Node.js]: Vue
Steps to Reproduce / Scenario:
Please attach logs to this issue:
N/A
Screenshots
The text was updated successfully, but these errors were encountered: