microsoft / vscode

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

Extension walkthrough doesn't pop up in new profile #226183

Open bamurtaugh opened 1 month ago

bamurtaugh commented 1 month ago

Part of https://github.com/microsoft/vscode-copilot/issues/5665

Using Windows 11 Insiders and latest VS Code Insiders:

Version: 1.93.0-insider (user setup)
Commit: e1db90f81da28c0994b5d50dc2b51e964359e62d
Date: 2024-08-21T05:04:11.586Z
Electron: 30.3.1
ElectronBuildId: 9960165
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.25987

If I try with fresh user and extensions directory, the Copilot walkthrough pops up without issue, and I would've expected a Profile to also be a fresh start.

bhavyaus commented 4 weeks ago

Makes sense. I'll work on updating this scenario.

aiday-mar commented 3 weeks ago

So I am currently testing the getting started scenario. I created a new profile with no extensions and empty settings. When I clicked on install Github Copilot, the extension main page opened. Is this is walkthrough page that is mentioned in the golden scenario TPI?

The view I have:

Screenshot 2024-08-27 at 12 33 32

I am on macOS Sonoma 14.6.1 (23G93) and Insiders

Version: 1.93.0-insider (Universal)
Commit: ff7a154d5e5e9034914f0466420f0f1407f0c95e
Date: 2024-08-27T05:04:20.235Z (5 hrs ago)
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0
bamurtaugh commented 3 weeks ago

Is this is walkthrough page that is mentioned in the golden scenario TPI?

@aiday-mar this is great feedback. What you see in the screenshot you shared is the README, which is different from the walkthrough the scenario refers to (supposed to be the getting started experience the completions extension contributes):

Image

I'll make sure this distinction is clearer in the scenario doc since your question totally makes sense. And your experience (only getting README and not getting started walkthrough experience) is in-line with what I experienced in this issue.