internal/chartconfig: add mod and remove bzr from go/vcs counter Add 'mod' to cover the case when none of the other VCSes are being used. This is possible as mentioned at https://go.dev/ref/mod#vcs-find: > vcs is the version control system. It must be one of the tools listed > in the table below or the keyword mod, which instructs the go command > to download the module from the given URL using the GOPROXY protocol. Remove 'bzr' since this counter's minimum version is Go 1.27, which is the same version that had bzr support removed from the go command (per proposal go.dev/issue/78090), so it'll never get a chance to trigger. For golang/go#76801. For golang/go#78090. Change-Id: I24003c75cadd0e364f52383bc64856970d815c49 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/774580 LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Roland Shoemaker <roland@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
This repository holds the Go Telemetry server code and libraries, used for hosting telemetry.go.dev and instrumenting Go toolchain programs with opt-in telemetry.
Warning: this repository is intended for use only in tools maintained by the Go team, including tools in the Go distribution and auxiliary tools like gopls or govulncheck. There are no compatibility guarantees for any of the packages here: public APIs will change in breaking ways as the telemetry integration is refined.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
The git repository is https://go.googlesource.com/telemetry.
The main issue tracker for the telemetry repository is located at https://go.dev/issues. Prefix your issue with “x/telemetry:” in the subject line, so it is easy to find.
This repository uses eslint to format TS files, stylelint to format CSS files, and prettier to format TS, CSS, Markdown, and YAML files.
See the style guides:
It is encouraged that all TS and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npm install./npm run all