-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Point docs link to v4
#524
Conversation
It's very confusing that when I land directly on `https://pkg.go.dev/github.com/golang-migrate/migrate` I get a the message: > You are look at a deprecated version, use the latest version instead But when I click the `latest version` link, it goes to a completely dead/wrong place. So I think for almost anyone who actually wants to look at the real docs, it's a lot simpler to link straight to `v4` by default. If they want a different version, they can change that. But let's have the default point to a helpful place, and then you can go looking for the broken version, rather than the other way around.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
README.md
Outdated
@@ -1,5 +1,5 @@ | |||
[![CircleCI - Build Status](https://img.shields.io/circleci/build/github/golang-migrate/migrate/master)](https://circleci.com/gh/golang-migrate/migrate) | |||
[![GoDoc](https://godoc.org/github.com/golang-migrate/migrate?status.svg)](https://godoc.org/github.com/golang-migrate/migrate) | |||
[![GoDoc](https://godoc.org/github.com/golang-migrate/migrate?status.svg)](https://pkg.go.dev/github.com/golang-migrate/migrate/v4) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also update the image link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, didn't realize they now exposed those directly... updated! I used the Github web UI which doesn't allow squashing, so please squash on merge.
I dropped the ?status.svg
as it appears to work fine without that, but if you want me to put it back let me know.
I also wasn't sure if I needed to append /v4
to the end of the image URL... it looks the same both ways, so I thought simpler to leave w/o so that if there's ever a v5
only the actual link needs updating, not the image link.
It's very confusing that when I land directly on
https://pkg.go.dev/github.com/golang-migrate/migrate
I get a the message:But when I click the
latest version
link, it goes to a completely dead/wrong place.So I think for almost anyone who actually wants to look at the real docs, it's a lot simpler to link straight to
v4
by default. If they want a different version, they can change that. But let's have the default point to a helpful place, and then you can go looking for the broken version, rather than the other way around.