Skip to content

Fix Monarch tutorial links#3817

Open
GavinWongYF wants to merge 1 commit intopytorch:mainfrom
GavinWongYF:fix-links-3811
Open

Fix Monarch tutorial links#3817
GavinWongYF wants to merge 1 commit intopytorch:mainfrom
GavinWongYF:fix-links-3811

Conversation

@GavinWongYF
Copy link
Copy Markdown

Fixes #3811

Description

Fixed two broken links in the Monarch tutorial: intermediate_source/monarch_distributed_tutorial.rst.

On Mar 31, 2026, the Monarch documentation migrated to a multi-version structure (see Monarch PRs #3328, #3333). This removed the root-level /generated/ paths, causing the original links in the tutorial to 404.

I have updated the links to the latest stable version v0.4.0, which I have verified to work now.
I checked for a /stable/ or /latest/ alias, but the upstream repo hasn't implemented these redirects yet; I will communicate with the Monarch maintainers and update accordingly once those aliases become available.

Checklist

  • The issue that is being fixed is referred in the description (see above "Fixes #ISSUE_NUMBER")
  • Only one issue is addressed in this pull request
  • Labels from the issue that this PR is fixing are added to this pull request
  • No unnecessary issues are included into this pull request.

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot bot commented Apr 4, 2026

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3817

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Apr 4, 2026

Hi @GavinWongYF!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla meta-cla bot added the cla signed label Apr 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broken links detected in docs 🔗

1 participant