[Docs] Add a structured issue form for ExecuTorch deployment stories
@mergennachin is already working on this.
Since Sep 10, 2026.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Problem
The success-stories documentation asks the community to submit production deployments, case studies, integrations, and demos, but the repository has no structured intake form. Free-form reports often omit deployment status, target hardware, backend, measurable results, public evidence, or publication permission.
A new GitHub issue form was drafted during #22620, but it changes repository issue configuration and is intentionally excluded so that PR remains documentation-only.
Proposed change
Add .github/ISSUE_TEMPLATE/success-story.yml with fields for project status, organization and product, workload, model and target, results, public sources, and publication permission. Apply the existing module: doc label.
Test plan
- Validate the YAML with the repository linters.
- Preview the issue form in GitHub.
- Submit a test issue and confirm required fields and automatic labeling.
cc @nil-is-all @byjlw
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.