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
{{ message }}
Repository navigation
x/pkgsite: support viewing a package @master #36811
Hence only godoc.org works as a means of viewing "current" docs for github.com/moby/moby/client.
Reacted by Martin Tournoij, Simon Law, Zik Aeroh, Chris K, Karol Marcjan, Ingo Oeser, Adam Chalkley, Antoine GIRARD, Gregory Petrosyan, Lomanic and 11 more
Note. This will also automatically fetch the module for the proxy and populate it on pkg.go.dev, if it does not already exist (per instructions at https://go.dev/about#adding-a-package). It may take a minute or two for the package to appear on pkg.go.dev, if it is not already there.
We know that this isn't the best user experience, and are working on a better workflow.
How about a "Fetch latest version from master" link added to the bottom of pages on pkg.go.dev in similar fashion to the "Refresh now" link of godoc.org?
Are there limits to this? With the exception of the example you posted, none of the common packages I use appear to work. They all use vanity URLs, so maybe this has something to do with it?
Oh, apparently I have to "request" them or it 404s? I hadn't visited the actual page to click the link. I don't know what that means, but it's confusing
The reason is because code.soquee.net/otp@master and mellium.im/xmpp@master weren't in our database yet. In the future, visiting these pages will automatically refresh master.
a lot of repositories are now moving to renaming their default branches to main. It seems that master is hard-coded in pkgsite. Would it be possible to support some kind of magic version string that gets the default branch, whatever it may be named? This may end up being the reason that I move some of my repos back to master, which I'd like to avoid.
Let me know if I should open another issue for this.
Activity
[-]go.dev: github.com/moby/moby/client docs are not current[/-][+]go.dev: support viewing <import-path>@master[/+][-]go.dev: support viewing <import-path>@master[/-][+]go.dev: support viewing a package @master[/+]julieqiu commentedon Jan 28, 2020
We're actively working on designing a better flow, but the workaround for this right now is to do the following:
https://proxy.golang.org/github.com/moby/moby/@v/master.info currently shows:
Note. This will also automatically fetch the module for the proxy and populate it on pkg.go.dev, if it does not already exist (per instructions at https://go.dev/about#adding-a-package). It may take a minute or two for the package to appear on pkg.go.dev, if it is not already there.
pkg.go.dev/<import-path>@<semantic-version>for the package documentation, in this case:https://pkg.go.dev/github.com/moby/moby/client@v1.4.2-0.20200128034134-2ebaeef943cc.
We know that this isn't the best user experience, and are working on a better workflow.
mewmew commentedon Feb 24, 2020
How about a "Fetch latest version from master" link added to the bottom of pages on
pkg.go.devin similar fashion to the "Refresh now" link ofgodoc.org?This is issue #37106
all: add redirect from /pkg.go.dev to pkg.go.dev/cuelang.org/go@$version
all: add redirect from /pkg.go.dev to pkg.go.dev/cuelang.org/go@$version
all: add redirect from /pkg.go.dev to pkg.go.dev/cuelang.org/go@$vers…
53 remaining items
julieqiu commentedon Jul 30, 2020
You can now view a package at master using the URL,
https://pkg.go.dev/<path>@master. For example, https://pkg.go.dev/github.com/moby/moby/client@master.SamWhited commentedon Jul 30, 2020
Are there limits to this? With the exception of the example you posted, none of the common packages I use appear to work. They all use vanity URLs, so maybe this has something to do with it?
julieqiu commentedon Jul 30, 2020
@SamWhited - mind sharing what they are? I can look into it.
SamWhited commentedon Jul 30, 2020
@julieqiu here are two of mine that appear to be exhibiting this behavior: https://pkg.go.dev/code.soquee.net/otp@master or https://pkg.go.dev/mellium.im/xmpp@master
SamWhited commentedon Jul 30, 2020
Oh, apparently I have to "request" them or it 404s? I hadn't visited the actual page to click the link. I don't know what that means, but it's confusing
julieqiu commentedon Jul 30, 2020
The reason is because
code.soquee.net/otp@masterandmellium.im/xmpp@masterweren't in our database yet. In the future, visiting these pages will automatically refresh master.Feel free to file a new issue with any UI suggestions.
hugelgupf commentedon Sep 10, 2020
Hi @julieqiu,
a lot of repositories are now moving to renaming their default branches to
main. It seems that master is hard-coded in pkgsite. Would it be possible to support some kind of magic version string that gets the default branch, whatever it may be named? This may end up being the reason that I move some of my repos back tomaster, which I'd like to avoid.Let me know if I should open another issue for this.
Thanks!
myitcv commentedon Sep 10, 2020
@hugelgupf - this issue is closed. Please open a new issue.
FWIW the means by which
gitcan determine the default remote (originin this case) branch looks like this:which then updates the following:
anacrolix commentedon Nov 11, 2020
In my experience, this only seems fixed for vanity URLs. More general module names don't work, like https://pkg.go.dev/github.com/anacrolix/torrent@master.
anacrolix commentedon Oct 7, 2021
This is broken for https://pkg.go.dev/github.com/anacrolix/torrent@master, is it related to this?
go mod tidy