-
Notifications
You must be signed in to change notification settings - Fork 607
Add FAQs and Common Issues doc page #7547
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/pytorch/executorch/7547
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 1 PendingAs of commit c3b6b81 with merge base 4796da7 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
# FAQs and Common Issues | ||
|
||
This page summarizes frequently asked questions and provides guidance on issues that commonly occur when adopting ExecuTorch. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also remind the user to check https://github.com/pytorch/executorch/issues and https://github.com/pytorch/executorch/discussions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea. I will add that as a follow-up today.
Summary
Add "FAQs and Common Issues" page to the ExecuTorch docs. This summarizes common issues that we've seen when users adopt ExecuTorch, as well as trends I've found looking through the last 6 months of GitHub and Meta-internal questions and issues.
I've tentatively put this under the Getting Started section, as that seems like the most reasonable place to put it, but I'm open to suggestions.
Test plan
New doc page preview: https://docs-preview.pytorch.org/pytorch/executorch/7547/getting-started-faqs.html.
For some reason, the doc job doesn't seem to re-run when updating the PR. I've re-build locally to check.