You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... for the syntax suggested in "go help importpath" (no ".git" suffixing the url)
I've managed to make private repos work by appending ".git" to the url. However this complicates things since the filesystem install path will now include the ".git". Also, the import statements must then have it.
There are tons of questions about this issue (or private repos in general) all over stackoverflow etc. etc. and many answers or posts give confusing or old information that makes go hard to use for newcomers. The go packaging is hard enough to grasp for newcomers as it is; combine that with these private repo issues and the result is no doubt three times as difficult.
The text was updated successfully, but these errors were encountered:
adg
changed the title
add support to "go get" for private bitbucket repos
cmd/go: add support to "go get" for private bitbucket repos
Jun 2, 2015
... for the syntax suggested in "go help importpath" (no ".git" suffixing the url)
I've managed to make private repos work by appending ".git" to the url. However this complicates things since the filesystem install path will now include the ".git". Also, the import statements must then have it.
There are tons of questions about this issue (or private repos in general) all over stackoverflow etc. etc. and many answers or posts give confusing or old information that makes go hard to use for newcomers. The go packaging is hard enough to grasp for newcomers as it is; combine that with these private repo issues and the result is no doubt three times as difficult.
The text was updated successfully, but these errors were encountered: