4 ms·

Go get does not start with a git clone. If you go get example.org/pkg/foo go fetches https://example.org/pkg/foo?go-get=1 https://example.org/pkg/foo?go-get=1.

• simoncion 11y ago
  > Go get does not start with a git clone. Fair enough. (I don't use go, so I'm unaware of pretty much all of its internals.) [0] > ...coordination between go and github could implement something for deprecated repositories without changing anything in git. A couple of things: * This only fixes things for Golang. It doesn't fix it for the couple-thousand other tools that pull things from Github. * I never suggested changing things in git. That would be freaking nuts. :) EDIT: Or did you mean "without changing anything in the git repo"? If you meant that, then I strike this bullet point and apologise for the noise. :) * Frankly, having a well-known file in your Git repo that contains meaningful tags seems far more compatible than changing git, or altering the $BUILD_TOOL<->GitHub integration... for one thing, the convention could be trivially adopted by non-git users. :) [0] Thanks for the documentation link, BTW! :D