Once you forked it, you have to change all the imports across the repo, and then it's kinda either very hard to make Pull Requests, or pull the new commits from the original repo.
This is one thing I really dislike about go dependencies.
If you have a solution for this, let me know, I would be very interested to know more about it.
But overall, I love go. I use it all the time anyway.
I threw together an example of doing this with `dep`. I forked Fatih's color package, and am using it as `github.com/fatih/color` no problem: https://github.com/sofuture/colortest (forked dep here: https://github.com/sofuture/color)
It works for you because it's a small project and you are not actually importing other of your own packages inside it.
But if you look at "echo", it import some other "echo" packages inside of it.
Edit: I'll fork echo in my example and show you.
Using the original package name: https://github.com/sofuture/colortest/blob/master/main.go#L7
I can refer to my fork: https://github.com/sofuture/colortest/blob/master/Gopkg.toml...
Thank you for the example :)
Echo is using some imports to their own packages inside the project.
IE: https://github.com/labstack/echo/blob/a098bcd3b0c445dde3d380...
So if I fork "echo", I have to replace the urls in their imports so it imports my fork packages.