[release] prepare v0.29.0 release

5bbdabb test/integration/goTest: log suspicious tests
6d4d3bf src/goInstallTools: use `go install -v` instead of `go install -x`
dbf1440 goDeveloperSurvey: update link and start/end date
9a0cabf settings: update for gopls/v0.7.3
ee7c340 goLanguageServer: print out all GOPATHs when there are multiple
656865d src/goInstallTools: use `go install` for go1.16+
af8377d goSurvey: update language in Go Developer survey prompt
8ac427b test: fix broken debugger tests
bdb0b61 src/goTest: visualize profiles
1f4e83b package.json: update mocha & run npm audit fix
4e2e945 src/goDebugConfiguration: handle directory with '.' in its name
337e533 src/goTest: show test output on run
1f8bf32 src/goTest: add single-test debugging
afc7d07 goSurvey: add a setting to disable all survey prompts
a90d590 src/goTest: update go.tests after resolving tests
e01db48 goDeveloperSurvey: prompt vscode-go users for the Go dev survey
5691e02 src/goDebugFactory: add program filepath to program error message
9b3e92e CHANGELOG.md: v0.28.1 note
5ecabf9 src/goTest: populate tests for open docs on start
079e752 src/goTest: ensure that cursorOrPrevious always saves
11afec4 src/goInstallTools: bugfix for grammar
bf9a5a1 src/goImpl: allow `-` as an acceptable char for interface names (package/variable)
cfee3e1 src/goDebugConfiguration: take program verbatim with external adapter
022e403 package.json: add showLog/logOutput/dlvFlags to go.delveConfig setting
6f98706 src/goTest: add view for profiles
b82ed6c package.json: start v0.29.0-dev
0f196ff package.json: support testAtCursor (and co.) despite codelenses

Change-Id: I36daf79425451ef500ad5a45301c9f2631700fa0
tree: 4c421d07a87c26206740806bd1631fdb0ada5572
  1. .github/
  2. .vscode/
  3. build/
  4. docs/
  5. languages/
  6. media/
  7. snippets/
  8. src/
  9. syntaxes/
  10. test/
  11. third_party/
  12. tools/
  13. typings/
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.json
  17. .gitignore
  18. .prettierrc.js
  19. .prettierrc.json
  20. .vscodeignore
  21. CHANGELOG.md
  24. README.md
  25. SECURITY.md
  26. go.mod
  27. go.sum
  28. package-lock.json
  29. package.json
  30. tsconfig.json

Go for Visual Studio Code


The VS Code Go extension provides rich language support for the Go programming language.

Quick Start

Welcome! 👋🏻
Whether you are new to Go or an experienced Go developer, we hope this extension fits your needs and enhances your development experience.

  • Step 1. If you haven't done so already, install Go and the VS Code Go extension.
  • Step 2. To activate the extension, open any directory or workspace containing Go code. Once activated, the Go status bar will appear in the bottom left corner of the window and show the recognized Go version.
  • Step 3. The extension depends on a set of extra command-line tools. If they are missing, the extension will show the “⚠️ Analysis Tools Missing” warning. Click the notification to complete the installation.

You are ready to Go :-)    🎉🎉🎉

Please be sure to learn more about the many features of this extension, as well as how to customize them. Take a look at Troubleshooting and Help for further guidance.

If you are new to Go, this article provides the overview on Go code organization and basic go commands. Watch “Getting started with VS Code Go” for an explanation of how to build your first Go application using VS Code Go.


This extension provides many features, including IntelliSense, code navigation, and code editing support. It also shows diagnostics as you work and provides enhanced support for testing and debugging your programs. See the full feature breakdown for more details and to learn how to tune its behavior.

In addition to integrated editing features, the extension provides several commands for working with Go files. You can access any of these by opening the Command Palette (Ctrl+Shift+P on Linux/Windows and Cmd+Shift+P on Mac), and then typing in the command name. See the full list of commands provided by this extension.

⚠️ Note: the default syntax highlighting for Go files is provided by a TextMate rule embedded in VS Code, not by this extension.


The extension uses a few command-line tools developed by the Go community. In particular, go, gopls, and dlv must be installed for this extension to work correctly. See the tools documentation for a complete list of tools the extension depends on.

In order to locate these command-line tools, the extension searches GOPATH/bin and directories specified in the PATH environment variable (or Path on Windows) with which the VS Code process has started. If the tools are not found, the extension will prompt you to install the missing tools and show the “⚠️ Analysis Tools Missing” warning in the bottom right corner. Please install them by responding to the warning notification, or by manually running the Go: Install/Update Tools command.

Setting up your workspace

Go modules are how Go manages dependencies in recent versions of Go. Modules replace the GOPATH-based approach to specifying which source files are used in a given build, and they are the default build mode in go1.16+. While this extension continues to support both Go modules and GOPATH modes, we highly recommend Go development in module mode. If you are working on existing projects, please consider migrating to modules.

Unlike the traditional GOPATH mode, module mode does not require the workspace to be located under GOPATH nor to use a specific structure. A module is defined by a directory tree of Go source files with a go.mod file in the tree's root directory.

Your project may involve one or more modules. If you are working with multiple modules or uncommon project layouts, you will need to configure your workspace by using Workspace Folders. Please see this documentation about supported workspace layouts.


The extension needs no configuration and should work out of the box. However, you may wish to adjust settings to customize its behavior. Please see the settings documentation for a comprehensive list of settings. See advanced topics for further customizations and unique use cases.


If the extension isn't working as you expect, you can take a look at our troubleshooting guides. There is one for general troubleshooting, and another specifically for troubleshooting the debugging feature.

Ask for help

If the troubleshooting guides did not resolve the issue, please reach out to us by filing an issue, starting a GitHub discussion, or by asking a question on Stack Overflow.

Also, you can take a look at go.dev/learn and golang.org/help for more general guidance on using Go.

Preview version

If you'd like to get early access to new features and bug fixes, you can use the nightly build of this extension. Learn how to install it in by reading the Go Nightly documentation.


We welcome your contributions and thank you for working to improve the Go development experience in VS Code. If you would like to help work on the VS Code Go extension, please see our contribution guide. It explains how to build and run the extension locally, and describes the process of sending a contribution.

Code of Conduct

This project follows the Go Community Code of Conduct. If you encounter a conduct-related issue, please mail conduct@golang.org.