Hongxiang Jiang

Next Change, with the extended functionality from relui, we will add a step to generate the vscode extension package This step will use `npx vsce .....` to create artifacts for...

Next change, we will use relui to create release note as draft for vscode-go release coordinator for review.  From the relui, the relui will print the url to the...

> I don't understand why the option has the higher priority than organize imports: Hi your-diary@, are you using vscode-go or vim-go. If you are using vscode-go, I think there...

Hi solomatov@, thank you for sharing your opinion. > My understanding is this action is available in every place where you could invoke code action in go files, am I...

Hi @caioreix I can confirm the sub test "Success" can not be correctly triggered using the code lenses provided. It end up using ``` Running tool: go test -timeout 30s...

cc @firelizzard18

Hi @firelizzard18 Thank you so much for your input here. I'm not familiar with testify framework but I'm glad to see that testify no longer require `-m / -testify.m` in...

In CL 645116, I saw vscode-go test is triggered against go 1.22 1.23 1.24 and gotip. The migration is done. I will mark this as closed.

> Is that intended? Yes. I believe so. Because vscode-go set go 1.23 in go.mod file so test with version that is lower than 1.23 is skipped. (Otherwise, it will...

Just realized there are some extra work needed in vscode-go refs/meta/config branch to add LUCI Result +1 as submission requirement. I will create another CL for this. Sorry for closing...