pytorch - 💡(How to fix) Fix PyTorch Docathon 2026! [1 participants]

We are excited for you to participate in the PyTorch docathon. This year we have the following repositories participating:

• pytorch/pytorch
• pytorch/tutorials
• pytorch/executorch

Date and location

• WHEN: The docathon starts on May 5 10 AM PST. Please do not work on tasks until then.
• WHERE: Virtual
• WHAT: Issues with the docathon-2026 label - will be posted on May 5th at 10 AM.

Watch our YouTube livestream to learn more details about the event.

Can everyone participate?

We encourage everyone to consider participating in the docathon but there are a few things we expect from the participants:

• You must have a GitHub account and know how to use Git and GitHub, how to submit or rebase your PR on the latest main branch, how to fork or clone the repo, how to view errors in the CI and troubleshoot. We reserve the right to reject incorrectly submitted PRs.
• You must be familiar with Python, the basics of Machine Learning, and have at least a basic knowledge of PyTorch. Familiarity with Sphinx, sphinx-gallery, and reStructuredText is a plus.
• Please use AI responsibly. We encourage participants to leverage the power of Artificial Intelligence (AI) tools to enhance their contributions to the PyTorch Docathon. AI can be an invaluable resource for tasks such as drafting clear explanations, refining grammar and style, summarizing complex concepts, and even generating code examples. However, participants must exercise responsibility and ethical judgment when incorporating AI-generated content and fixes. Reach out to the PyTorch docs team for any questions on Discord.
  Before you start contributing make sure to read Linux Foundation Code of Conduct as well as the GitHub Code of Conduct.

Useful resources

• The Ultimate Guide to PyTorch Contributions
• Docstring Guidelines
• Building the Documentation

What contributions are we looking for?

All issues for this docathon are tagged with the docathon-2026 label. Please note that contributions that address other issues won't be counted. We are primarily looking for the following contributions:

• Documentation bug fixes
• Tutorial fixes and testing
• Contributions to the ExecuTorch repo

NOTE: Due to the large number of RSVPs, the tasks are provided on a first come first serve basis. Please don't hoard the tasks!

Difficulty Levels

The issues have three levels of difficulty: easy, medium, and advanced. If this is your first time contributing to PyTorch, we recommend that you start with an issue that is tagged as easy.

How to contribute to tutorials?

1. Read PyTorch Contributor Document for general guidelines on how the submission process works and overall style and voice.

2. Pick an issue that is labeled as docathon-2026.

3. In the issue, add a comment with the text /assigntome. If the issue is already assigned, please find another issue to work on. We ask that you assign one issue at a time - we want to give everyone a fair chance to participate. When you are done with one issue and get it approved, you can assign another one to yourself and start working on it.

4. Fork or clone the PyTorch repository to your computer. For simple fixes, like incorrect URLs, you could use the GitHub UI as well.

5. Create a branch and work on the fix.

6. Test your fix by running the single tutorial locally. Don't run the whole build as it takes hours and requires a GPU. You can run one tutorial as a script:

   python3 <tutorial-name.py> or GALLERY_PATTERN="neural_style_transfer_tutorial.py" make html

7. Make sure to pay attention to the PyTorch Docstring Guidelines as this will affect your PR.8.After you fix all the issues, you are ready to submit your PR.

   NOTE: In PyTorch, we enforce lint rules on code in order to help us catch common mistakes and enforce a greater degree of uniformity in our codebase than human reviewers can normally enforce. You can find more information regarding PyTorch lintrunner and how to run it here.

Submiting Your PR

1. Submit your PR referencing the issue you've picked. For example:
2. If you have not yet, sign the Contributor License Agreement (CLA) - prompted as a check in the PR. We can't accept any PRs without a signed CLA.
3. Watch for any CI errors and fix as needed - all checks must pass successfully.
4. When the build is finished, you will see a preview link to preview your changes.
5. The reviewers might provide feedback that we expect you to address.
6. When all feedback is addressed and your PR is approved - one of the reviewers will merge your PR.

Top contributors recognition

For all contributions addressing the docathon-2026 issues merged to the main branch in the participating repos during the period from May 5 to May 17, 5PM PST, you will get a PyTorch Docathon GitHub badge. The issues will be released on the first day of the docathon. The top contributors will receive additional recognition and will be featured in a PyTorch social media announcement. In addition to the main repo and tutorials, this year, we will explicitly recognize a top contributor in each participating library repository, such as the ExecuTorch repo.

Questions?

You can find a lot of useful information in the The Ultimate Guide to PyTorch Contributions. You can also post your questions in the docathon Discord Server.

cc @sekyondaMeta @AlannaBurke