You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case was to add a new version of a package and the instructions do not explicitly mention this case. The second and third variant in the instructions under "adding package" seem to refer to a specific version, so I guess they can be used to update to a new major version of the package. The first variant at least cannot.
My suggestion to improve the text is to add a condition when the "request" buttons is shown, e.g. make it read like:
Try the page you expect on pkg.go.dev, which will offer a “Request” button
in case the package is not listed at all. Then click it. For example:
A different way to fix this would be to mention how packages are updated instead of added.
Would adding the version string or an additional example with the version string make it clear?
Adding a package
Data for the site is downloaded from [proxy.golang.org](https://proxy.golang.org/).
We monitor the [Go Module Index](https://index.golang.org/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:
Visiting that page on pkg.go.dev, and clicking the “Request” button. For example:
Feedback is required from experts, contributors, and/or the community before a change can be made.
Issue is not actionable because of missing required information, which needs to be provided.
Jun 6, 2023