It has nothing to do with gitolite.
Gitolite is just an authorization layer, which will accept or deny your
git clone/push/pull command, depending on your username.
If you can declare a git repo as a source for go, you can use it.
Gitolite will just check who you are, but won't otherwise affect how that repo is used with go.
The thing with go, is that it pulls the repo name from the directory structure, so for instance:
is automagically transformed into
git clone github.com/me/myproject.
But how can gitolite names be transformed into a path?
I don't think you need to transform anything: if go is able to contact your git repo (GitHub or any other hosting repo server), gitolite will intercept the command and validate it (or deny it).
You can plug gitolite on top of ssh or (as it is the case with git request done by go import) with https.
But the main point is:
- gitolite is on the server side
- you should use it with an Apache sever (like, for instance, with my config), and not ssh, if you want to easily have your repos accessed with go imports.