microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
164.17k stars 29.28k forks source link

Manage trusted extensions don't work #208208

Closed rsbmk closed 7 months ago

rsbmk commented 7 months ago

Type: Bug

I try to manage two GitHub accounts in VS Code, my personal account (for GitHub copilot) and my job account (for pull request extension) and I want to disable permissions account for these extensions but “Manage trusted extensions” don't disabled permissions for extensions

VS Code version: Code 1.87.2 (Universal) (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:21:31.043Z) OS version: Darwin x64 23.0.0 Modes:

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|1, 2, 2| |Memory (System)|16.00GB (0.42GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
Extensions (15) Extension|Author (truncated)|Version ---|---|--- vscode-tailwindcss|bra|0.10.5 codium|Cod|0.7.52 vscode-eslint|dba|2.4.4 gitlens|eam|14.9.0 prettier-vscode|esb|10.1.0 copilot|Git|1.175.0 copilot-chat|Git|0.13.1 vscode-pull-request-github|Git|0.82.1 headwind|hey|1.7.0 vscode-env|Iro|0.1.0 color-highlight|nau|2.8.0 px-to-rem|sai|1.3.1 errorlens|use|3.16.0 vscode-import-cost|wix|3.3.0 material-theme|zhu|3.17.0
rsbmk commented 7 months ago

https://github.com/microsoft/vscode/assets/64700838/23d5c472-0dd9-4990-ac00-595643d33b99

TylerLeonhardt commented 7 months ago

These checkboxes are actually disabled because these extensions are extensions that we ship so they are trusted as a part of our platform. This will be more clear in the next version of VS Code (and the current version of VS Code Insiders) where they will actually be rendered as disabled: https://github.com/microsoft/vscode/pull/208159

The heart of this issue is that VS Code only supports being logged in to a single GitHub account. If you have 2+, this is not a supported experience at this time. We do want to officially support multiple GitHub accounts in the near future! When we do, the experience of deciding what extension uses what account will be smoother. See https://github.com/microsoft/vscode/issues/127967

TylerLeonhardt commented 7 months ago

/duplicate https://github.com/microsoft/vscode/issues/127967

vscodenpa commented 7 months ago

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

northsea4 commented 7 months ago

@TylerLeonhardt

The heart of this issue is that VS Code only supports being logged in to a single GitHub account. If you have 2+, this is not a supported experience at this time. We do want to officially support multiple GitHub accounts in the near future! When we do, the experience of deciding what extension uses what account will be smoother. See https://github.com/microsoft/vscode/issues/127967

I clearly remember not long ago that it was possible to use different Github accounts for different extensions. For example, account A is used for "Github Pull Requests" and account B is used for "Copilot". But now, when I log into a Github, vscode forces me to use the latest Github account for both extensions, which means I may not be able to use the Copilot extension, or I may not be able to see the account I need to view PRs.