Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: add support to "go get" for private bitbucket repos #11032

Closed
petri opened this Issue Jun 2, 2015 · 3 comments

Comments

Projects
None yet
6 participants
@petri
Copy link

petri commented 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.

@adg 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

@adg adg closed this Jun 2, 2015

@adg adg reopened this Jun 2, 2015

@ianlancetaylor ianlancetaylor added this to the Go1.6 milestone Jun 3, 2015

@jimdoescode

This comment has been minimized.

Copy link

jimdoescode commented Oct 3, 2015

It would be really great to have a way of distributing internal bitbucket dependencies.

@rsc

This comment has been minimized.

Copy link
Contributor

rsc commented Nov 5, 2015

What exactly do you think we should do?

Why don't private bitbucket repos work already?

@bcmills

This comment has been minimized.

Copy link
Member

bcmills commented Jan 23, 2019

#27344 is a duplicate but has more detail. Consolidating into that issue.

@bcmills bcmills closed this Jan 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.