#I noticed that the Github dependency

1 messages · Page 1 of 1 (latest)

ivory skiff
#

cc @modest plover any thoughts? Since you've been working with this

modest plover
# ivory skiff cc <@274903880343748619> any thoughts? Since you've been working with this

Hi, yes. It was in discussion between Andrea and Sam. Basically, we weren't sure on how Dagger Github would scrape our libraries for this dependents field. We are scraping above library, to make sure we don't lose data, but we're also scraping: https://github.com/dagger/dagger-go-sdk/network/dependents. It is the proper dagger.io/dagger of the SDK. [this is the price to pay with our current proxyfication of the SDKs releases (Go mod issues)]

As requested by Solomon, I am also extending the scraper to pkg.dev.go list (today), as it contains repos not shown in the Dependents

molten jackal
#

yeah there's also https://pkg.go.dev/dagger.io/dagger?tab=importedby (this might be what you're referring to @modest plover ?) but it'll only include packages indexed by pkg.go.dev, so i wouldn't expect it to cover much; i'd guess most things using dagger are internal tools/scripts that people don't look at API docs for