When I first started using go I also was a bit annoyed at the fact that I had to have everything in my gopath, particularly when I forked a repo as none of the

When I first started using go I also was a bit annoyed at the fact that I had to have everything in my gopath, particularly when I forked a repo as none of the paths would lead to my fork. I've since started to also organize all of my code the gopath way and I just set $GOPATH to $HOME. When forking I just add a new remote and work out of the upstream repo, which seems saner now as it reduces object duplication. I don't know if I will ever move away from organizing my node this way if I can help it. > That said, mod allows you to put your project anywhere but in the GOPATH I don't know if I've run into this yet, though the only project[0] I've used gomod with has a makefile so it might do something to handle it. [0] https://github.com/ipfs/go-ipfs https://github.com/ipfs/go-ipfs