Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: go mod init no longer attempts to import requirements from other tools' configuration files #71537

Open
hoelzro opened this issue Feb 3, 2025 · 1 comment
Assignees
Labels
Documentation Issues describing a change to documentation. GoCommand cmd/go NeedsFix The path to resolution is known, but the work has not been done.

Comments

@hoelzro
Copy link

hoelzro commented Feb 3, 2025

The documentation for go mod init mentions running the command will try importing module requirements from other tools' configuration files:

If a configuration file for a vendoring tool is present, init will attempt to import module requirements from it. init supports the following configuration files.

This feature was (understandably) removed in Go 1.22, so the docs just need a little updating!

@gabyhelp
Copy link

gabyhelp commented Feb 3, 2025

Related Code Changes

Related Documentation

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

@gabyhelp gabyhelp added the Documentation Issues describing a change to documentation. label Feb 3, 2025
@seankhliao seankhliao added NeedsFix The path to resolution is known, but the work has not been done. GoCommand cmd/go labels Feb 3, 2025
@thepudds thepudds self-assigned this Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Issues describing a change to documentation. GoCommand cmd/go NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

4 participants