-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Fix #155022 rst to markdown conversion #155540
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/155540
Note: Links to docs will display an error until the docs builds have been completed. ⏳ 17 Pending, 1 Unrelated FailureAs of commit c2ed40f with merge base 4a954fc ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot label "topic: docs" |
@pytorchbot label "topic: not user facing" |
These pages have Created On changed to Jun 09, 2025, this needs to be fixed: |
How exactly can we fix this? I did use I don't see how you can get Git to think it is the same file unless you modify the file with multiple commits... and since git thinks it's a new file, the "Created On" time which is extracted from git log will not track the original file. |
Try splitting the commits. First, make one commit for the git mv (file move/rename). Then, make a separate commit to update the file format. This approach works well for me. |
Only git mv func.ux_limitations, func.whirlwind_tour, and futures because after rst-markdown conversion, git thinks we deleted and added new files. The conversion changes will come in a second commit/PR.
3314e47
to
c405b0a
Compare
Split into 2 commits (this is the second one) so that we maintain the git log of these files.
@pytorchbot drci |
@pytorchbot merge -f "Docs only change. Doc signal is green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Used rst2myst tool
Fixes #155022
Docs comparison (check out the 'new' whenever docs build)
cc @svekars @sekyondaMeta @AlannaBurke