Fix the RTD docs links from PyPI title and badge - #291
Merged
Conversation
This shows up on GH and PyPI, being a part of the core packaging metadata. The currently present link is broken and shows an HTTP 404 Not Found. The patch fixes that. The change is [handwritten by a human](https://github.com/sponsors/webknjaz). It is similar to but *different* from tox-dev#290 which requires elevated admin-level in-repo privileges and probably cannot be automated (though one could attempt having a pet agent use GH CLI to handle that I suppose).
gaborbernat
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This shows up on GH and PyPI, being a part of the core packaging metadata. The currently present link is broken and shows an HTTP 404 Not Found. The patch fixes that. The change is handwritten by a human.
It is similar to but different from #290 which requires elevated admin-level in-repo privileges and probably cannot be automated (though one could attempt having a pet agent use GH CLI to handle that I suppose).