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
TL;DR: I moved my package to a custom domain and used the HTML meta go-import to ensure go get still works: https://goyave.dev/goyave . The repo has been moved from my personal account to an organization. Therefore, import paths changed (from github.com/System-Glitch/goyave/v3 to goyave.dev/goyave/v3). I tried to request pkg.go.dev to generate the new docs using this link: https://pkg.go.dev/goyave.dev/goyave/v3@v3.7.0 . I clicked the "Request " button.
What did you expect to see?
I expected go.pkg.dev to generate the new docs just like if it was a new module.
What did you see instead?
For some reason, it doesn't find the repository. And when I go to https://pkg.go.dev/goyave.dev/goyave/v3 (without specifying version), it redirects me to the previous location.
The text was updated successfully, but these errors were encountered:
What is the URL of the page with the issue?
https://pkg.go.dev/goyave.dev/goyave/v3@v3.7.0
What is your user agent?
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0
Screenshot
What did you do?
Context: go-goyave/goyave#129
TL;DR: I moved my package to a custom domain and used the HTML meta
go-import
to ensurego get
still works: https://goyave.dev/goyave . The repo has been moved from my personal account to an organization. Therefore, import paths changed (fromgithub.com/System-Glitch/goyave/v3
togoyave.dev/goyave/v3
). I tried to request pkg.go.dev to generate the new docs using this link: https://pkg.go.dev/goyave.dev/goyave/v3@v3.7.0 . I clicked the "Request " button.What did you expect to see?
I expected go.pkg.dev to generate the new docs just like if it was a new module.
What did you see instead?
For some reason, it doesn't find the repository. And when I go to https://pkg.go.dev/goyave.dev/goyave/v3 (without specifying version), it redirects me to the previous location.
The text was updated successfully, but these errors were encountered: