-
Notifications
You must be signed in to change notification settings - Fork 267
non-master branches not being recognised #464
Comments
https://gotools.org/srcd.works/go-billy.v1 works okay, so this is indeed a gddo-specific issue. My first guess was to check
So the issue must be elsewhere and will require further investigation. Spinning up a local instance of gddo, or looking in the log entries, is probably the fastest way to figure out what it is. Edit: Here's some output from trying this on a local instance:
(This is assuming the latest master version is deployed to production, but I'm pretty sure |
gddo uses default "master" tag for custom domain, while yours doesn't have a "master". Maybe we should change the behavior to match "go get"? |
I believe we should. I don't see a reason why godoc.org/<import path> shouldn't be able to display documentation for some <import path> that |
@shantuo I can change |
Not sure if this is the best place to discuss this, but the behavior of non-master branches not being recognized is also present on go-talks.appspot.com. The |
@smasher164 Given that it uses slightly different code (although also in |
The introduction of Go modules is making this issue more critical: I've had to switch the default branch of the Goa repository (github.com/goadesign/goa) to match the branch that contains the latest major version of the Go module ( |
@raphael For full module support, you should use pkg.go.dev. See golang/go#33654 (comment) for more information about it. |
Great, thank you for the pointer. |
I am trying to generate the documentation for a custom domain:
.works
but I get a 404:https://godoc.org/srcd.works/go-billy.v1
The text was updated successfully, but these errors were encountered: