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
quickDiff setting is ignored #4726
Comments
@nathaniel-palmer-simplisafe did you reload after setting |
@alexr00 Yes I did |
I could also repro because I had the old setting |
It would still be helpful to have a way to switch between PR and local changes globally rather than having to toggle between them when viewing individual changes although that would probably work better as a command rather than a setting. Would it make sense to open that as a feature request here or on the main VSCode repo? |
@nathaniel-palmer-simplisafe can you confirm that this is the flow you want?
|
@alexr00 Yes |
Opened microsoft/vscode#180691 |
Where are the |
To verify:
|
@alexr00 Just a heads up: the settings changes related to quickdiffs aren't picked up without reloading the vscode window |
Type: Bug
When
githubPullRequests.quickDiff
is disabled I still see the quick diff annotations in the gutter for PR changes even after reloading VSCode. Sometimes I have a PR checked out locally that I'm still working on and without this setting I can't use the gutter annotations to reliably tell what I've changed locally.Extension version: 0.62.0
VS Code version: Code 1.77.3 (Universal) (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:19:37.325Z)
OS version: Darwin x64 22.4.0
Modes:
Sandboxed: No
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: