We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
semantic import versioning: explicitly mention including '/vN' in 'go get' commands.
Restore modules wiki page.
Destroyed Modules (markdown)
Noting that athens.azurefd.net is an experimental server
adjust repo name in Quick Start
adjust directory name in Quick Start
update name of binary in Quick Start section
show initializing git in the Quick Start section. The connection between repo location and module path is something people sometimes miss when ramping up on modules.
Added go-mod-outdated in Community tools
Updated Modules (markdown)
Format: Are there "always on" module repositories and enterprise proxies?
Remove extraneous word
add FAQ on using a go.mod to exclude large or unnecessary files from a module
Added akyoto/mgit to community tools
Add goproxy.io
update table of contents to point to new FAQs
add FAQ on repos that have opted in to modules without applying semver tags
mention 'go list -mod=readonly all' technique in FAQ on troubleshooting versions of a your dependency
mention GOPROXY performance benefits as an alternative to creating a multi-module repository
Minor spelling/formatting fixes
add FAQ on set of steps to resolve "parsing go.mod: unexpected module path" error caused by a mismatch between import paths vs. declared module identity
add section on avoiding breaking import paths in migrating to modules section
update FAQ on replace: mention 'go.mod' is required for file system target, and 'require' is now optional
Replace bullet points with paragraphs on "When should I use the replace directive?" FAQ's section
update vendoring FAQ to also mention a 'vendor' directory can provide dependencies to Go 1.11+ when module-mode is disabled
clarify prelease tag behavior and slightly reorganize 'How to Upgrade' section
Clarify that go get -u ignores pre-releases