commit | 481f2b5d3f84bfa23bed3bdfdea934a122082cb5 | [log] [tgz] |
---|---|---|
author | Hana (Hyang-Ah) Kim <hyangah@gmail.com> | Thu Dec 28 17:49:41 2023 -0500 |
committer | Hyang-Ah Hana Kim <hyangah@gmail.com> | Thu Jan 04 23:03:48 2024 +0000 |
tree | 52ce8fc1d66035bdd4cbaa570b83bedf625def02 | |
parent | 4d53cdc646ccff2baabfc8820878cee5b8f9f4b4 [diff] |
build: add GCB release workflow This workflow is meant to replace the GitHub action workflow defined in https://github.com/golang/vscode-go/blob/master/.github/workflows/release.yml The GH workflow was a collection of command line tools invocation and some bash scripting to parse the version tag and adjust the workflow depending on whether it's for rc or not. I figured it's easier to work with go, so ported the logic to build/release.go. TODO: convert most part of build/all.bash and the nightly release workflow with go code. release.go uses `gh` (GitHub CLI tool) to post the release note and the artifacts (vsix) to GitHub. Dockerfile is updated to include `gh`. Reference: https://stackoverflow.com/a/69477930 The workflow needs to access GitHub personal access token. To access the release API, write permission for Content & Workflow is necessary. https://docs.github.com/en/rest/authentication/permissions-required-for-fine-grained-personal-access-tokens?apiVersion=2022-11-28#repository-permissions-for-contents Tested it by triggering the GCB workflow against a forked repo. For b/216321767 Change-Id: I1eec6b4b896fe1f1565bbf9e160f0368cade36c7 Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/553115 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Suzy Mueller <suzmue@golang.org> Commit-Queue: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: kokoro <noreply+kokoro@google.com>
The VS Code Go extension provides rich language support for the Go programming language.
Welcome! 👋🏻
Whether you are new to Go or an experienced Go developer, we hope this extension fits your needs and enhances your development experience.
Install Go 1.18 or newer if you haven't already.
Install the VS Code Go extension.
Open any directory or workspace containing Go code to automatically activate the extension. The Go status bar appears in the bottom left corner of the window and displays your Go version.
The extension depends on go
, gopls
, dlv
and other optional tools. If any of the dependencies are missing, the ⚠️ Analysis Tools Missing
warning is displayed. Click on the warning to download dependencies.
See the tools documentation for a complete list of tools the extension depends on.
You are ready to Go :-) 🎉🎉🎉
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.
See the full feature breakdown for more details.
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.
For better syntax highlighting, we recommend enabling semantic highlighting by turning on Gopls' ui.semanticTokens
setting. "gopls": { "ui.semanticTokens": true }
The VS Code Go extension supports both GOPATH
and Go modules modes.
Go modules are used to manage 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+. 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. See the Supported workspace layouts documentation for more information.
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.
VS Code Go extension relies on the Go Telemetry to learn insights about the performance and stability of the extension and the language server (`gopls``). Go Telemetry data uploading is disabled by default and can be enabled with the following command:
go run golang.org/x/telemetry/cmd/gotelemetry@latest on
After telemetry is enabled, the language server will upload metrics and stack traces to telemetry.go.dev. You can inspect what data is collected and can be uploaded by running:
go run golang.org/x/telemetry/cmdgotelemetry@latest view
If we get enough adoption, this data can significantly advance the pace of the Go extension development, and help us meet a higher standard of reliability. For example:
These are just a few ways that telemetry can improve gopls. The telemetry blog post series contains many more.
Go telemetry is designed to be transparent and privacy-preserving. If you have concerns about enabling telemetry, you can learn more at https://telemetry.go.dev/privacy.
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, see our contribution guide to learn how to build and run the VS Code Go extension locally and contribute to the project.
This project follows the Go Community Code of Conduct. If you encounter a conduct-related issue, please mail conduct@golang.org.