Originally we thought we were going to require 3.17, but we backed off.
For golang/go#67001
Change-Id: I9979f018f534638e911bfefb17747973c3948781
Reviewed-on: https://go-review.googlesource.com/c/website/+/611943
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Daniel Martí <mvdan@mvdan.cc>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Tim King <taking@google.com>
Thanks to Bill Morgan for pointing them out.
Change-Id: I81affbdf006baa5274efa121b837e2bedf97bad5
Reviewed-on: https://go-review.googlesource.com/c/website/+/612256
Auto-Submit: Ian Lance Taylor <iant@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Eli Bendersky <eliben@google.com>
Reviewed-by: Tim King <taking@google.com>
Change-Id: I92daee0c86d00ae15a5859d158652feb1214f7f5
Reviewed-on: https://go-review.googlesource.com/c/website/+/611797
Auto-Submit: Ian Lance Taylor <iant@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Commit-Queue: Ian Lance Taylor <iant@google.com>
Otherwise we get a trailing blank line, which is not what we want.
Pointed out by dmitshur in CL 611655.
Change-Id: I6c2c0cbc6e19c06d392ce6e6fd108163020bd124
Reviewed-on: https://go-review.googlesource.com/c/website/+/610565
Commit-Queue: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Ian Lance Taylor <iant@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Lines returns a iter.Seq, not iter.Seq2,
so there's only one value to range over.
Change-Id: I37ea040c73b469978a2e1a78f6436775a7b63d80
Reviewed-on: https://go-review.googlesource.com/c/website/+/611655
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fixesgolang/go#69215
Change-Id: I708e7af6790969444afc0527775643d4c42c90c3
Reviewed-on: https://go-review.googlesource.com/c/website/+/611155
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Hyang-Ah Hana Kim <hyangah@gmail.com>
Change-Id: I0ee4a16d8422be4d542f1e4ea2de0f456fca383d
Reviewed-on: https://go-review.googlesource.com/c/website/+/610802
Auto-Submit: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Michael Pratt <mpratt@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
One of the examples was no longer racy. Change the example
to use a variable declared outside of the loop, to make it racy.
Fixesgolang/go#69261
Change-Id: I79d5c9372d4badbdaccdea53e8b395291805dc47
Reviewed-on: https://go-review.googlesource.com/c/website/+/610975
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Commit-Queue: Ian Lance Taylor <iant@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Update the telemetry documentation to suggest the `go telemetry`
subcommand for managing telemetry configuration, rather than the
`gotelemetry` command.
Also make it a little more prominent how to revert to local mode.
Change-Id: I6e2353223fe9ef49002eda953ad8d3c277196891
Reviewed-on: https://go-review.googlesource.com/c/website/+/610315
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Auto-Submit: Robert Findley <rfindley@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Add a blog post to provide an update on telemetry in the Go 1.23
toolchain and gopls.
Change-Id: Ie3d253a6100a752628c1265906e317d01e26436b
Reviewed-on: https://go-review.googlesource.com/c/website/+/605075
Reviewed-by: Ian Lance Taylor <iant@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Russ Cox <rsc@golang.org>
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
These files are not served on the website. They haven't changed since
they were added in 2021 in CL 356511. We have a new security page that
covers what we want to say.
Change-Id: I24be0e1b4c6aef10ae5f8f0c1b2d3329d1688ac7
Reviewed-on: https://go-review.googlesource.com/c/website/+/604915
Auto-Submit: Ian Lance Taylor <iant@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Eli Bendersky <eliben@google.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
The RangefuncExperiment wiki page has been updated to reflect the fact
that range-over-func is in 1.23, and the wiki page is no longer a good
destination for describing the change. Drop the link to it.
Add a link to the recent blog post.
Change-Id: I899f36f4172182b7089f4964e426530fd1865778
Reviewed-on: https://go-review.googlesource.com/c/website/+/608819
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Ian Lance Taylor <iant@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Thanks to Scott Kirkwood for pointing it out.
Change-Id: Id5d46b5ca5619b40aa6585ff85cd8ee26f8e4fb6
Reviewed-on: https://go-review.googlesource.com/c/website/+/608895
Auto-Submit: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Alan Donovan <adonovan@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Change-Id: Ib78e629854a0e9bc4fb287d539649a3ad5b7c58b
Reviewed-on: https://go-review.googlesource.com/c/website/+/607935
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Michael Pratt <mpratt@google.com>
Reviewed-by: David Chase <drchase@google.com>
Reviewed-by: Alan Donovan <adonovan@google.com>
Reviewed-by: Eli Bendersky <eliben@google.com>
Using 'go mod edit -go=1.23' is equivalent to editing the go directive
in go.mod, and nothing more. This doesn't pay attention to the rest of
go.mod content and may leave the module in an untidy state.
Prior to Go 1.21, 'go mod tidy -go=1.23' was the suggested way to do
the update while also maintaining the tidy state of the module. That
form is still valid, but the simpler go get go@1.23 is now preferred¹.
The 'go get go@1.n' syntax is newer and not everyone has seen it yet,
so keep the 'go mod edit' mention with a hint as to how they differ.
¹ https://go.dev/doc/toolchain#get, second last paragraph
Change-Id: I5c8c5568e1512fec4de28e666a6b80be98290647
Reviewed-on: https://go-review.googlesource.com/c/website/+/607036
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Change-Id: I12bfca1a22b94af33668beca6d8ee7ba216ea913
Reviewed-on: https://go-review.googlesource.com/c/website/+/605536
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Alan Donovan <adonovan@google.com>
Reviewed-by: Eli Bendersky <eliben@google.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Go blog posts have metadata like:
by:
- Author Name
- Maybe Another Author
Those YAML lists were decoded into a slice of empty interfaces, each
holding a string, and all that was being ignored. Update it to parse
the []any type of p["by"] and to return an error if there aren't any
authors. There are only 2 existing blog posts that cause such errors,
but they're very old and can be ignored (or updated if needed).
There's probably more that can be done, like having one <author> XML
item per 'by' item in the YAML/JSON metadata of blog posts, but this
is a reasonable step forward.
For golang/go#68869.
Change-Id: I7b97a09b006bacf4835442a749cb0e467c7dbb47
Reviewed-on: https://go-review.googlesource.com/c/website/+/605537
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Hongxiang Jiang <hxjiang@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Fixesgolang/go#68891
For golang/go#64207
For golang/go#65614
Change-Id: I9256d9de0687b9e3cf674b4d318f4d5023a9bf16
Reviewed-on: https://go-review.googlesource.com/c/website/+/605875
Reviewed-by: Carlos Amedee <carlos@golang.org>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Go was introduced to ByteDance in 2014, and since then engineering teams across ByteDance have adopted Go to build products and services on a massive scale.
Change-Id: I1554da05c15c3cc1f4a07414bb488764c8e2e3dd
GitHub-Last-Rev: b6e24d5a64
GitHub-Pull-Request: golang/website#287
Reviewed-on: https://go-review.googlesource.com/c/website/+/592715
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Cameron Balahan <cbalahan@google.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Change-Id: I5d12653af8f377ff20d1c8f955634e9cb9c01ea2
GitHub-Last-Rev: 5660e19d3d
GitHub-Pull-Request: golang/website#268
Reviewed-on: https://go-review.googlesource.com/c/website/+/553955
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Auto-Submit: Ian Lance Taylor <iant@google.com>
Change-Id: I63a3ac96dc56d46e948586c871c42b4c9b950e9f
Reviewed-on: https://go-review.googlesource.com/c/website/+/603796
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This change:
Removes the draft notice from go1.23.md
Updates the deployment for golangorg to Go 1.23
Adds Go 1.23 to history/release.go
For golang/go#65614
Change-Id: I5afe34461fdb764b8f9759b0b8d894f72532ecf1
Reviewed-on: https://go-review.googlesource.com/c/website/+/605175
Reviewed-by: David Chase <drchase@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
It's no longer needed as of the Go 1.22 release.
Fixesgolang/go#68808
Change-Id: Ib968a414703d28c1d4b4c5300bb5c697264b639e
Reviewed-on: https://go-review.googlesource.com/c/website/+/604575
Reviewed-by: Carlos Amedee <carlos@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
Reviewed-by: Rob Pike <r@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Briefly describe pidfd, and note the extra opened file descriptors as
per request in [1].
[1]: https://github.com/golang/go/issues/62654#issuecomment-2170992329
Updates golang/go#62654.
For golang/go#65614.
Co-authored-by: Michael Pratt <mpratt@google.com>
Change-Id: Ie2a8e917cbbb1c6129a1706c22c9993222855bc4
Reviewed-on: https://go-review.googlesource.com/c/website/+/603717
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Michael Pratt <mpratt@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Michael Pratt <mpratt@google.com>
All blog posts for major Go releases include a dot, other than the one
for Go 1.2. Fix the inconsistency and add a redirect from the old page.
Change-Id: I2f08142b6e802808be49adb5abf1562ab2d6fd73
Reviewed-on: https://go-review.googlesource.com/c/website/+/603795
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Change-Id: If55ced63c7cd5becc2dbd1e2ce35af0d5e29abe4
GitHub-Last-Rev: ba9b266857
GitHub-Pull-Request: golang/website#295
Reviewed-on: https://go-review.googlesource.com/c/website/+/601515
Auto-Submit: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
When there are no security fixes (or no bug fixes) in a given release,
it's represented with a nil *FixSummary. Since it also may reasonably
be represented with an empty FixSummary, add a test to enforce one of
the two possible styles is consistently chosen. The template handles
an empty non-nil *FixSummary as a very generic "there were some fixes"
text, which is never what we want.
Change-Id: I96ac7cdf37ec7a8406f31500024150df422730bb
Reviewed-on: https://go-review.googlesource.com/c/website/+/603495
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
The old https://blogs.dropbox.com is inaccessible.
Change-Id: I48de0ea61be4ea7954d461a1bea4e6d3b6cfd785
Reviewed-on: https://go-review.googlesource.com/c/website/+/602836
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: David Chase <drchase@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Change-Id: I8fe0452619ed588d17bb12c413ca11f3b1d9aded
Reviewed-on: https://go-review.googlesource.com/c/website/+/602835
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: David Chase <drchase@google.com>
I had a small discussion with @ianlancetaylor here:
https://groups.google.com/g/golang-nuts/c/uon32LDerjM/m/dvg0mxbwAAAJ?utm_medium=email&utm_source=footer
I would like to clarify this entry about method sets a bit because the current explanation is a bit confusing. I believe there is no reason for the Write method of Buffer to use a value receiver. In this case, the sentence about the compiler's ability to implicitly take addresses doesn't make sense.
What I believe is implied here is a hypothetical situation where the code from the example is allowed by Go, and then it is noted that this makes no sense as the result would be lost in the caller.
Change-Id: Ie4de77364165d59178e2b1e6e1393370e06d1755
GitHub-Last-Rev: 40392d43f0
GitHub-Pull-Request: golang/website#296
Reviewed-on: https://go-review.googlesource.com/c/website/+/601996
Auto-Submit: Ian Lance Taylor <iant@google.com>
Reviewed-by: Rob Pike <r@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
I'm part of the Gophers-Latam Community. I am excited to present our
translation of the Tour of Go, a collaborative effort of our community.
It's available at https://go-tour-lat.appspot.com/.
Fixesgolang/go#64454
Change-Id: Icd6e1f8ec340deea992858571c03bc2ae933d72b
GitHub-Last-Rev: 45234eb657
GitHub-Pull-Request: golang/website#264
Reviewed-on: https://go-review.googlesource.com/c/website/+/545855
Reviewed-by: Thiago Mowszet <thiagomowszet@gmail.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Change-Id: I49bad5dc6816241357546d68274acb1ea0fa8391
GitHub-Last-Rev: 27b48c2c47
GitHub-Pull-Request: golang/website#294
Reviewed-on: https://go-review.googlesource.com/c/website/+/601495
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
For golang/go#68526.
For golang/go#65614.
Change-Id: I260da94ffaae0d6583e6396b0a78b46dd298313c
Reviewed-on: https://go-review.googlesource.com/c/website/+/600936
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Tim King <taking@google.com>
Reviewed-by: Robert Griesemer <gri@google.com>
TryBot-Bypass: Robert Griesemer <gri@google.com>
These anchor links allow users to copy the links for jumping tos
the specific sections easily.
We use javascript to add these links to handle both .html
and .md file format contents. If we had only markdown-based
contents, we could've adjusted the markdown-to-html renderer
instead of relying on javascript. Alternatively, we can try
to rewrite the html in a later pass, but html dom query and
rewrite is simpler in JS.
In order to minimize styling changes in the header text,
we set up the anchor on ¶ symbol that appears only on hover.
This is similar to how pkg.go.dev handles header anchor links.
Adjust the code for TOC generation (in godocs.js), since
now the heading elements include ¶, we want to drop it but
use the first part of the heading elements when compiling
TOC.
Fixesgolang/go#68596
Change-Id: Idfe4734c54c636e426b579fdcd697156e87b5747
Reviewed-on: https://go-review.googlesource.com/c/website/+/601055
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Rob Pike pointed out that it could be clearer and more self-contained,
as well as being clear about generic methods never happening.
Change-Id: I854a38e20b4a7cd695bb3fa0a237759c5f7224d3
Reviewed-on: https://go-review.googlesource.com/c/website/+/599475
Auto-Submit: Russ Cox <rsc@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Add this file now so that it's possible to preview the latest release
notes draft at https://tip.golang.org/doc/go1.24, and to include that
link in the tracking issue. Based on CL 588057 that did this for 1.23.
For golang/go#68545.
Change-Id: I07f30023d23ec027927f7417ebece4110f221efa
Reviewed-on: https://go-review.googlesource.com/c/website/+/600179
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
For golang/go#65614.
Change-Id: Iecdebfaf4e7467734e60f30867ebcf926e31e97b
Reviewed-on: https://go-review.googlesource.com/c/website/+/599775
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Fixesgolang/go#67659
Change-Id: I01b22c68049f89694513185ac9076e4fa8d94114
Reviewed-on: https://go-review.googlesource.com/c/website/+/598095
Reviewed-by: Ian Lance Taylor <iant@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Cherry Mui <cherryyz@google.com>
Commit-Queue: Ian Lance Taylor <iant@golang.org>
This is a grammar rules that my fingers will never learn, and sometimes
my eyes do not notice...
Change-Id: If6c5e8b45702844996f13802ffb041d0e7d6a322
Reviewed-on: https://go-review.googlesource.com/c/website/+/598696
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
A common use-case for reading the telemetry documentation is to discover
how to enable or disable telemetry, yet the configuration section is
somewhat far down the page.
Add a new info callout with quick commands to enable or disable
telemetry.
For golang/go#68204
Change-Id: I6efc366401e626ed436905bda35fe75ae1c4bc57
Reviewed-on: https://go-review.googlesource.com/c/website/+/598695
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Very minor tweaks:
- Remove (c) pseudosymbol.
- Remove "All Rights Reserved."
- Change "Google Inc." (no longer exists) to "Google LLC".
[git-generate]
echo '
,s/\(c\) //
,s/ All rights reserved.//
,s/Google Inc./Google LLC/
w
q
' | sam -d LICENSE
Change-Id: I01330570f8d0a932becb8464519182970fdd48f3
Reviewed-on: https://go-review.googlesource.com/c/website/+/598590
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Russ Cox <rsc@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Eli Bendersky
Ian Lance Taylor
cuishuang
Gopher Robot
Alice Merrick
Hana (Hyang-Ah) Kim
Dmitri Shuralyov
Deleplace
Rob Findley
Sean Liao
Michael Anthony Knyszek
Guangming Luo
Alexey Shamrin
David Chase
Carlos Amedee
Kir Kolyshkin
Will Faught
Oleksandr Redko
wdesert
Brad Fitzpatrick
Thiago
Robert Griesemer
Russ Cox
Cherry Mui