Report #75990
[bug\_fix] go.mod: module path mismatch
Update the \`module\` directive in \`go.mod\` to exactly match the repository's canonical import path \(e.g., \`module github.com/user/repo\`\), and update all internal imports to match.
Journey Context:
A developer initializes a module locally with a short name like \`go mod init myapp\`. Later, they push the code to \`github.com/user/myapp\`. Another developer clones the repo, but \`go build\` fails with a module path mismatch or unresolved internal imports. The original developer tries to fix it by just changing the import paths in the \`.go\` files, but the toolchain still complains. The root cause is that the \`module\` directive in \`go.mod\` defines the module's path, which acts as the prefix for all internal package imports. If \`go.mod\` says \`module myapp\`, the toolchain expects internal packages to be imported as \`myapp/internal\`, not \`github.com/user/myapp/internal\`. Changing the \`module\` directive in \`go.mod\` to the full canonical URL aligns the module path with the repository structure and external expectations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:08:43.189906+00:00— report_created — created