3 ms·

That does not work in the old godoc.org either: https://godoc.org/git.lukeshu.com/go/libfastimport https://godoc.org/git.lukeshu.com/go/libfastimport So that'

That does not work in the old godoc.org either: https://godoc.org/git.lukeshu.com/go/libfastimport https://godoc.org/git.lukeshu.com/go/libfastimport So that's not against pkg.dev. Did somebody look into why? Anyway it seems that the repo was not added to pkg.dev automatically: https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 and the automatic fetching should work now: https://github.com/golang/go/issues/37002 https://github.com/golang/go/issues/37002

arp242 6y ago
> Anyway it seems that the repo was not added to pkg.dev automatically: > > https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 The way this works (or rather, worked) is that you first need to "go get" a module and then it gets picked up by the pkg.go.dev system. This works like that for every site, and was kind weird and confusing, although as you mentioned this was improved on recently. Either way: not related to that module being on sr.ht; that's just coincidental.
ddevault 6y ago
See my comment here which explains how "go-source" works: https://news.ycombinator.com/item?id=24024130 https://news.ycombinator.com/item?id=24024130 It doesn't work on godoc.org not because they don't recognize your domain, but because cgit doesn't have go-source meta tags.
- throwayws 6y ago
  There was a proposal to add a new go-source-2 meta tag, but that was abandoned because a lot of code hosting sites would not have been supported yet: https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/40477 https://github.com/golang/go/issues/40477 That is why they decided to turn it into an internal/source package inside pkgsite first to have test cases for a later go-source-2. If your site does not show source links on pkg.go.dev then add a comment to issue 40477 above and an exception will be added. - internal/source: https://github.com/golang/pkgsite/blob/master/internal/source/source.go https://github.com/golang/pkgsite/blob/master/internal/sourc... Note1: Maybe mention this on your website because that took a little to find. It does not fit into the narrative though. Note2: Requiring frontends to offer meta tags is the only way to make code discoverable with the url alone. cgit not offering this is on cgit and not on Go/pkgsite (haven't checked whether they do)

arp242 6y ago

> Anyway it seems that the repo was not added to pkg.dev automatically: > > https://github.com/golang/go/issues/38326 https://github.com/golang/go/issues/38326 The way this works (or rather, worked) is that you first need to "go get" a module and then it gets picked up by the pkg.go.dev system. This works like that for every site, and was kind weird and confusing, although as you mentioned this was improved on recently. Either way: not related to that module being on sr.ht; that's just coincidental.

ddevault 6y ago

See my comment here which explains how "go-source" works: https://news.ycombinator.com/item?id=24024130 https://news.ycombinator.com/item?id=24024130 It doesn't work on godoc.org not because they don't recognize your domain, but because cgit doesn't have go-source meta tags.

throwayws 6y ago
There was a proposal to add a new go-source-2 meta tag, but that was abandoned because a lot of code hosting sites would not have been supported yet: https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/39559 https://github.com/golang/go/issues/40477 https://github.com/golang/go/issues/40477 That is why they decided to turn it into an internal/source package inside pkgsite first to have test cases for a later go-source-2. If your site does not show source links on pkg.go.dev then add a comment to issue 40477 above and an exception will be added. - internal/source: https://github.com/golang/pkgsite/blob/master/internal/source/source.go https://github.com/golang/pkgsite/blob/master/internal/sourc... Note1: Maybe mention this on your website because that took a little to find. It does not fit into the narrative though. Note2: Requiring frontends to offer meta tags is the only way to make code discoverable with the url alone. cgit not offering this is on cgit and not on Go/pkgsite (haven't checked whether they do)