From ad346cd87f71dcd462d7cdcf86544aeb637061e2 Mon Sep 17 00:00:00 2001 From: joecummings Date: Tue, 2 Dec 2025 07:46:42 -0800 Subject: [PATCH 1/3] Add new feature request template --- .github/ISSUE_TEMPLATE/feature-request.yml | 57 ++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/feature-request.yml diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml new file mode 100644 index 000000000..0f8e0c5eb --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature-request.yml @@ -0,0 +1,57 @@ +name: ✨ Feature Request +description: Suggest a new feature or enhancement for this project + +body: +- type: markdown + attributes: + value: > + #### Before submitting a feature request, please search through [existing issues](https://github.com/meta-pytorch/forge/issues?q=is%3Aissue+sort%3Acreated-desc+) to see if something similar has already been proposed. +- type: textarea + attributes: + label: 🎯 Context/Motivation + description: | + Describe the problem you're trying to solve or the use case for this feature. + What is the motivation behind this request? Why would this feature be valuable? + placeholder: | + Example: "When training large models, I often need to..." + validations: + required: true +- type: textarea + attributes: + label: 💡 What does this look like in pseudo-code? + description: | + Provide a rough sketch of what the API or implementation might look like. + This helps us understand your vision for how the feature would work. + placeholder: | + ```python + # Example pseudo-code showing how you envision using this feature + model = MyModel() + result = model.new_feature(...) + ``` + validations: + required: false +- type: textarea + attributes: + label: ✅ Acceptance Criteria + description: | + What would need to be true for this feature to be considered complete? + List the key requirements or behaviors expected. + placeholder: | + - [ ] The feature should support X + - [ ] It should handle edge case Y + - [ ] Documentation is updated + validations: + required: true +- type: textarea + attributes: + label: 📝 Additional Context + description: | + Add any other context, screenshots, examples, or references that would help explain the feature request. + placeholder: | + Links to similar implementations, research papers, or other relevant information. + validations: + required: false +- type: markdown + attributes: + value: > + Thanks for contributing 🎉! From f54eb0b1c19cf0ffb64a37354f727ee3c302f8a7 Mon Sep 17 00:00:00 2001 From: joecummings Date: Wed, 3 Dec 2025 08:55:39 -0800 Subject: [PATCH 2/3] Mark psuedo code and acceptance criteria as optional --- .github/ISSUE_TEMPLATE/feature-request.yml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml index 0f8e0c5eb..a4db18c2c 100644 --- a/.github/ISSUE_TEMPLATE/feature-request.yml +++ b/.github/ISSUE_TEMPLATE/feature-request.yml @@ -11,14 +11,13 @@ body: label: 🎯 Context/Motivation description: | Describe the problem you're trying to solve or the use case for this feature. - What is the motivation behind this request? Why would this feature be valuable? placeholder: | Example: "When training large models, I often need to..." validations: required: true - type: textarea attributes: - label: 💡 What does this look like in pseudo-code? + label: 💡 [Optional] What does this look like in pseudo-code? description: | Provide a rough sketch of what the API or implementation might look like. This helps us understand your vision for how the feature would work. @@ -32,10 +31,9 @@ body: required: false - type: textarea attributes: - label: ✅ Acceptance Criteria + label: ✅ [Optional] Acceptance Criteria description: | What would need to be true for this feature to be considered complete? - List the key requirements or behaviors expected. placeholder: | - [ ] The feature should support X - [ ] It should handle edge case Y From fe8cc761893b8d99dd1bc0bc6bb15cda0dbc8a87 Mon Sep 17 00:00:00 2001 From: joecummings Date: Wed, 3 Dec 2025 09:05:38 -0800 Subject: [PATCH 3/3] Reduce drastically --- .github/ISSUE_TEMPLATE/feature-request.yml | 38 +++------------------- 1 file changed, 5 insertions(+), 33 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml index a4db18c2c..cfe8204b7 100644 --- a/.github/ISSUE_TEMPLATE/feature-request.yml +++ b/.github/ISSUE_TEMPLATE/feature-request.yml @@ -8,45 +8,17 @@ body: #### Before submitting a feature request, please search through [existing issues](https://github.com/meta-pytorch/forge/issues?q=is%3Aissue+sort%3Acreated-desc+) to see if something similar has already been proposed. - type: textarea attributes: - label: 🎯 Context/Motivation + label: Context/Motivation description: | - Describe the problem you're trying to solve or the use case for this feature. - placeholder: | - Example: "When training large models, I often need to..." + Describe the problem you're trying to solve or the use case for this feature. Include any relevant links and context. validations: required: true - type: textarea attributes: - label: 💡 [Optional] What does this look like in pseudo-code? + label: Pseudo-code + acceptance criteria [Optional] description: | - Provide a rough sketch of what the API or implementation might look like. - This helps us understand your vision for how the feature would work. - placeholder: | - ```python - # Example pseudo-code showing how you envision using this feature - model = MyModel() - result = model.new_feature(...) - ``` - validations: - required: false -- type: textarea - attributes: - label: ✅ [Optional] Acceptance Criteria - description: | - What would need to be true for this feature to be considered complete? - placeholder: | - - [ ] The feature should support X - - [ ] It should handle edge case Y - - [ ] Documentation is updated - validations: - required: true -- type: textarea - attributes: - label: 📝 Additional Context - description: | - Add any other context, screenshots, examples, or references that would help explain the feature request. - placeholder: | - Links to similar implementations, research papers, or other relevant information. + Provide a rough sketch of what the API or implementation might look like. This helps us understand your vision for how the feature would work. + Also, if possible, include what would need to be true for this feature to be considered complete. validations: required: false - type: markdown