hacking on gogs: info on how to be able to try your changes locally befo...

...re commiting them

Hello, today I tried to submit a patch to Gogs through a pull request and had some trouble compiling my forked repository.

The problem is that inside gogs' code you reference some sub-packages by their github url.
For example inside `cmd/web.go` the imports are:
```
        "github.com/gogits/gogs/routers"
        "github.com/gogits/gogs/routers/admin"
        "github.com/gogits/gogs/routers/api/v1"
        "github.com/gogits/gogs/routers/dev"
        "github.com/gogits/gogs/routers/org"
        "github.com/gogits/gogs/routers/repo"
        "github.com/gogits/gogs/routers/user"
```
I forked and cloned the repository to work on the file `routers/user/settings.go`. But when I did `go build`, go instead of using my `routers/user/settings.go` it used the package from <https://github.com/gogits/gogs/routers/user>.
So instead of compiling my code, I ended up compiling your code without knowing. It was a bit frustrating because I depend on the compiler output to validate my edits.

In this new page I describe how to trick the go tool to use the user's forked repository instead of yours.
I don't know if there is a better way to handle this. I just though this information may help someone.