Go
If you cannot publish a new version with retractions because the source code repository or domain name is no longer accessible, or if you want to hide documentation for all current and future versions, you can file a request for the pkgsite team to hide your package documentation from pkg.go.dev. Note that the package will continue to be available via go get or go install unless its module is retracted.
Présentation
Documentation is generated based on Go source code downloaded from the Go Module Mirror at proxy.golang.org//@v/.zip. New module versions are fetched from index.golang.org and added to pkg.go.dev site every few minutes.
Most of the time, pkg.go.dev can determine the location of a package’s source files, and provide links from symbols in the documentation to their definitions in the source. If your package’s source is not linked, try one of the following two approaches.
Data for the site is downloaded from proxy.golang.org. We monitor the Go Module Index regularly for new packages to add to pkg.go.dev. If you don’t see a package on pkg.go.dev, you can add it by doing one of the following:
The guidelines for writing documentation for the godoc tool apply to pkg.go.dev.
Most Go packages look and behave the same regardless of the machine architecture or operating system. But some have different documentation, even different exported symbols, for different architectures or OSes. Some packages may not even exist for some architectures.
Go calls an OS/architecture pair a “build context” and writes it with a slash, like linux/amd64.
Informations pratiques
- Informations mises à jour le
Fiche découverte par PHPBB Lab Bot. Page source — mer. 23 sept. 2026 07:40
