Hongxiang Jiang

Hi Sc00bz, I was not able to re-produce this issue, do you think this is something still happening? Do you think this is something related to VSCode? ``` ~/Desktop/codebase/gomodifytags/vulncheck/blah.go/ [main]...

As the first CL, we will create a new workflow which is responsible of creating a release candidate for the stable version of vscode-go extension. The input version should be...

Some offline sync with Hana and Dmitri, we want to adopt the approve functionality same as gopls release automation. And also use the cool drop down menu. The input of...

The next CL, we will add a step in gopls release process. Every gopls release will trigger a gopls version update in vscode-go repo.   The update will happen...

Next CL, the flow will create the release milestone and release issue. (only if there isn't one already created and open) The first run of the flow create this release...

Next CL, the vscode go release flow will try to create a release branch if not already exist. The current logic is, only create a branch if the input version...

Next CL, we will add a step in gopls release flow to update gopls version in vscode-go project. After a gopls release is done, both master branch and release branch...

Next Change, we will add a new flow for vscode-go insider version release When choosing this flow, this flow will figure out which insider version you should release. In the...

Next Change, we will add two steps in insider version release 1. Read the head commit from master branch 2. Wait for coordinator approval. Personally speaking, releasing from master branch...

The next CL, we will refactor the x/build so it can run cloud build using docker based image. This docker based cloud build will be used to trigger vscode-go test....