Hongxiang Jiang

Next change: add a gopls release tag to x/tools release branch. The coordinator will provide a semantic version as input to `gopls release flow`. This input version should follow the...

Next change: fix a bug where the cloud run is being triggered against the master branch but the script is being triggered against the release branch. 

Next change: for gopls release, after add the release tag to the x/tools, the last step is to update the dependency for master branch. This step only need to be...

Hi mythemeria, Thank you for reporting this issue. The go extension have some default behavior of formatting on save. Please see the [FAQ](https://github.com/golang/vscode-go/blob/master/docs/faq.md#how-can-i-stop-the-extension-from-formatting-files-on-save) here. If you follow instructions mentioned in...

Hi YesYouKenSpace, I find a [tool](https://help.gitkraken.com/gitlens/gitlens-settings/#remote-provider-integration-settings) offered from GitLens. I'm not sure if this is something you are looking for. If you configured correctly, you will find options below. But...

Hi jelmd, > Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools There is no such thing based on the statement above, I think the Go extension...

Hi myalcin81, Thanks for raising this. I'm not sure I fully understand your request. Are you saying you are working on multiple repos in this same time and you only...

Hi @Aatroy, Thanks for reporting the issue. I was not able to re-produce the issue you encountered. My experience is normally smooth. See `goDebugFactory.ts` the vscode go extension need to...

You can follow the contributing guide [here](https://github.com/golang/vscode-go/wiki/contributing#developing) Once you download the repo, you can launch another vscode with the developing version of go extension. Then you can test the behavior...

Seems like re appearance of https://github.com/golang/go/issues/74532