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
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.ymlwith fields for project status, organization and product, workload, model and target, results, public sources, and publication permission. Apply the existingmodule: doclabel.Test plan
cc @nil-is-all @byjlw