Add PyTorch 2.10 through 2.13 documentation support - #2723
Merged
Merged
Conversation
ring00
marked this pull request as ready for review
August 28, 2026 18:09
Add the four newer documentation releases and extract complete structured breadcrumbs used by the current PyTorch documentation theme. Keep the existing HTTP-based scraping workflow and cover structured, malformed, single-item, and legacy breadcrumb formats.
There was a problem hiding this comment.
🟢 Approval recommended
The version registrations and breadcrumb handling are consistent with the available documentation structure and preserve older-theme compatibility.
Pull request overview
Adds PyTorch documentation support for versions 2.10–2.13 and improves entry naming and categorization.
Changes:
- Registers four new PyTorch documentation versions.
- Prefers Schema.org breadcrumbs while retaining legacy fallbacks.
- Updates the attribution year to 2026.
File summaries
| File | Description |
|---|---|
lib/docs/scrapers/pytorch.rb |
Adds versions 2.10–2.13 and updates attribution. |
lib/docs/filters/pytorch/entries.rb |
Extracts structured breadcrumbs with fallback support. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Scrape the PyTorch documentation from a local copy instead of fetching thousands of pages from docs.pytorch.org on every run. The rendered HTML is published per version in the "site" branch of pytorch/docs, so document the sparse checkout in docs/file-scrapers.md. Skip non-HTML paths, since the published tree ships a .md source next to every .html page.
Check out the version being scraped from the "site" branch of pytorch/docs, which is what https://docs.pytorch.org serves. There is no documentation archive to download, and the branch holds every version at once, so the files are taken from a sparse clone rather than with #download_and_extract.
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
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 PR adds PyTorch documentation versions 2.10 through 2.13.
PyTorch's structured Schema.org breadcrumbs are now preferred when available, with the existing visible-breadcrumb parsing retained as a fallback for older versions. This restores the complete names of pages whose visible breadcrumbs are incomplete, such as Use
fullgraph=Trueto Identify and Eliminate Graph Breaks.Key changes:
Validation:
If you're updating existing documentation to its latest version, please ensure that you have:
SOURCEfile inpublic/icons/your_scraper_name/are up-to-date if the documentation has a custom iconself.linkscontains up-to-date urls ifself.linksis defined