Skip to content
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

Fixed dead link in posts/2023-08-29-committing-lockfiles.md #1172

Conversation

EliasHolzmann
Copy link

Said blog post contains a link to the Cargo book. The heading that was being linked to was changed from "Multiple requirements" to "Multiple version requirements" (in this commit), this change was not reflected in the blog post. I am not too sure whether the link has ever worked as the docs were changed on 2023-08-27 while the blog post was only written on 2023-08-29, but either way, this PR fixes the link.

Said blog post contains a link to the Cargo book. The heading that was being
linked to was changed from "Multiple requirements" to "Multiple version
requirements" (in [this commit][doc-change]), this change was not reflected in
the blog post. I am not too sure whether the link has ever worked as the docs
were changed on 2023-08-27 while the blog post was only written on 2023-08-29,
but either way, this commit fixes the link.

[doc-change]: rust-lang/cargo@01e1ff0?diff=unified&w=0#diff-d184a3240b09684abaca1a50dc8519dab2a9f5a17631180036f4b8090bb8a2d0L105
@weihanglo
Copy link
Member

This may also need to be fixed in cargo book by adding a redirection there

@EliasHolzmann
Copy link
Author

Thanks!

With this being fixed on the Cargo book side, I don't think this PR is necessary anymore (admittedly, the link now goes to a <p> above the heading and is therefore slightly too far up, but oh well, the average reader not focused on this detail probably won't even notice any difference). Therefore, I'm going to close this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants