Create feature_request.yml
This commit is contained in:
99
.github/ISSUE_TEMPLATE/feature_request.yml
vendored
Normal file
99
.github/ISSUE_TEMPLATE/feature_request.yml
vendored
Normal file
@@ -0,0 +1,99 @@
|
|||||||
|
# .github/ISSUE_TEMPLATE/feature_request.yml
|
||||||
|
name: Feature Request
|
||||||
|
description: Suggest a new feature or enhancement
|
||||||
|
title: "[FEAT] "
|
||||||
|
labels: ["enhancement"]
|
||||||
|
assignees:
|
||||||
|
- ${{github.actor}}
|
||||||
|
body:
|
||||||
|
- type: markdown
|
||||||
|
attributes:
|
||||||
|
value: |
|
||||||
|
Thanks for taking the time to propose a new feature!
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: problem
|
||||||
|
attributes:
|
||||||
|
label: Problem Statement
|
||||||
|
description: What problem are you trying to solve with this feature?
|
||||||
|
placeholder: I'm frustrated when trying to analyze different model results because I need to manually compare them...
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: solution
|
||||||
|
attributes:
|
||||||
|
label: Proposed Solution
|
||||||
|
description: Describe the solution you'd like to implement
|
||||||
|
placeholder: Create a visualization utility that automatically compares results across multiple models and experiments
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: alternatives
|
||||||
|
attributes:
|
||||||
|
label: Alternatives Considered
|
||||||
|
description: Describe alternatives you've considered
|
||||||
|
placeholder: I considered using an external tool, but integrating directly would provide better workflow
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
|
|
||||||
|
- type: dropdown
|
||||||
|
id: component
|
||||||
|
attributes:
|
||||||
|
label: Component
|
||||||
|
description: Which part of the thesis project would this feature affect?
|
||||||
|
options:
|
||||||
|
- LaTeX Document
|
||||||
|
- Python Source Code
|
||||||
|
- Jupyter Notebook
|
||||||
|
- Data Processing
|
||||||
|
- ML Model
|
||||||
|
- Visualization
|
||||||
|
- Build/Environment
|
||||||
|
- Multiple Components
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: dropdown
|
||||||
|
id: priority
|
||||||
|
attributes:
|
||||||
|
label: Priority
|
||||||
|
description: How important is this feature for your thesis progression?
|
||||||
|
options:
|
||||||
|
- Critical (blocks progress)
|
||||||
|
- High (significantly improves workflow)
|
||||||
|
- Medium (nice to have)
|
||||||
|
- Low (minor improvement)
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: implementation
|
||||||
|
attributes:
|
||||||
|
label: Implementation Ideas
|
||||||
|
description: Any initial thoughts on how to implement this feature?
|
||||||
|
placeholder: |
|
||||||
|
- Could use matplotlib's subplot feature
|
||||||
|
- Would need to standardize the model output format
|
||||||
|
- Should include statistical significance tests
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: benefits
|
||||||
|
attributes:
|
||||||
|
label: Expected Benefits
|
||||||
|
description: How will this feature benefit your thesis work?
|
||||||
|
placeholder: This will save time in analysis and provide more consistent comparisons across experiments
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: additional
|
||||||
|
attributes:
|
||||||
|
label: Additional Context
|
||||||
|
description: Any other context, screenshots, or reference material
|
||||||
|
placeholder: Here's a paper that uses a similar approach...
|
||||||
|
validations:
|
||||||
|
required: false
|
||||||
Reference in New Issue
Block a user