https://stackoverflow.com/questions/14323872/using-forked-pa...
There are a lot of different approaches listed in here that have changed over time. Different projects evolve at different rates. You might need to become familiar with multiple old ways of dependency management to be really effective.
I went to https://go.dev/doc/
I clicked on "Managing Dependencies" -> "Requiring external module code from your own repository fork"
And arrived at:
https://go.dev/doc/modules/managing-dependencies#external_fo...
Assuming that information is correct - and i'm not in a place to judge that, i just don't have the knowledge unfortunately - that journey felt pretty short and discoverable.
Apparently I’m remembering the old hell.
The replace directive seems to solve the issues with forked projects in particular. [1]
1 - https://github.com/golang/go/wiki/Modules#when-should-i-use-...
I don't understand how this is still a problem for people to understand. It's been the standard for literally years now.
It's actually even better now that go workspaces are a thing.
This is definitely a pain point I've had with golang and the 'accepted' process has changed 3 or 4 times in the last 2 years.
No it hasn't.