cmd/go: mod vendor should ignore non-Go content #44119
Open
Labels
Comments
This seems like a duplicate of #26366. |
Very old and unsolved, but yes, essentially the same issue. Don't know if, after all this time, it refers to the same implementation anymore. |
Is there a typo in the issue title? I'm having trouble figuring out what the desired behavior is here. |
I don't think so. What's your understanding of the expected behaviour? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tl;dr: Go is not the only tool I use in my project; I expect it share
vendor
peacefully.What version of Go are you using (
go version
)?(latest at the time of this writing)
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Ruby gems and Go modules "installed" in
vendor
.What did you see instead?
Only Go modules in
vendor
.Workaround
Bundler leaves Go modules alone, so re-running
bundle install
aftergo mod vendor
creates the desired state.The text was updated successfully, but these errors were encountered: