-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Unable to see settings sync on option in the "gear icon menu" #91875
Comments
Settings Sync is not yet enabled in insiders. We are planning to enable it in 1.44.0-insiders.
Which release notes do you mean and where did you find it? |
@sandy081, i am talking about the insiders build release notes: why is this issue closed? |
if so then what is this? Settings Sync Bootstrap VS Code using Settings Sync |
@sanket-bhalerao As mentioned in other issue We are preparing release notes for next major release (1.44.0) and we are making Settings Sync ready for preview from next insiders (1.44.0-insiders). I was completely forgotten that current insiders picks up this release notes. I will update the release notes and mention from which insiders it will be available from. Sorry for the confusion. |
Issue Type: Bug
The release notes for V1.43.0-insiders show the option however, I am still unable to see the settings sync option in the Gear icon menu.
is there some setting or flag I need to enable in order to check/use this feature?
VS Code version: Code - Insiders 1.43.0-insider (17c6d12, 2020-02-28T12:46:02.355Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 4.15.0-88-generic
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Extensions (26)
The text was updated successfully, but these errors were encountered: