Update issue templates
This commit is contained in:
parent
0b8e01ddb9
commit
4e62b2180e
4 changed files with 92 additions and 0 deletions
42
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
42
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
|
|
@ -0,0 +1,42 @@
|
|||
---
|
||||
name: Bug report
|
||||
about: Create a report to help us improve
|
||||
title: "[BUG]"
|
||||
labels: bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Describe the bug**
|
||||
A clear and concise description of what the bug is.
|
||||
## Issue Type
|
||||
|
||||
## Steps to Reproduce
|
||||
|
||||
1. **Environment Setup:**
|
||||
- OS: [e.g., Ubuntu 20.04]
|
||||
- Python Version: [e.g., 3.8.10]
|
||||
- Frameworks/Libraries: past output of `pip freeze` here
|
||||
- Colab / Script
|
||||
|
||||
2. **Dataset Details:**
|
||||
- Dataset Name:
|
||||
- Data Preprocessing Steps: [e.g., Tokenization with specific parameters]
|
||||
|
||||
3. **Model Details:**
|
||||
- Model ID:
|
||||
- Model Configuration: [e.g., lora params, quantization, etc.]
|
||||
|
||||
4. **Training Configuration:**
|
||||
- Trainer Args: `SFTConfig`, `GRPOConfig`
|
||||
|
||||
5. **Reproduction Steps:**
|
||||
- Minimal script to reproduce error
|
||||
|
||||
6. **Expected Behavior:**
|
||||
|
||||
7. **Actual Behavior:**
|
||||
- [e.g., Description of the error, unexpected results, or performance issues encountered]
|
||||
- [e.g., Error messages or logs]
|
||||
|
||||
8. **Additional notes:**
|
||||
10
.github/ISSUE_TEMPLATE/custom.md
vendored
Normal file
10
.github/ISSUE_TEMPLATE/custom.md
vendored
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
name: Custom issue template
|
||||
about: Describe this issue template's purpose here.
|
||||
title: ''
|
||||
labels: ''
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
|
||||
20
.github/ISSUE_TEMPLATE/documentation.md
vendored
Normal file
20
.github/ISSUE_TEMPLATE/documentation.md
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
name: Documentation
|
||||
about: Documentation request
|
||||
title: "[DOCUMENTATION]"
|
||||
labels: documentation
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Is your feature request related to a problem? Please describe.**
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
**Describe the solution you'd like**
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
**Describe alternatives you've considered**
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
|
||||
**Additional context**
|
||||
Add any other context or screenshots about the feature request here.
|
||||
20
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
20
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
name: Feature request
|
||||
about: Suggest an idea for this project
|
||||
title: "[FEAT]"
|
||||
labels: enhancement
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Is your feature request related to a problem? Please describe.**
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
**Describe the solution you'd like**
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
**Describe alternatives you've considered**
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
|
||||
**Additional context**
|
||||
Add any other context or screenshots about the feature request here.
|
||||
Loading…
Add table
Add a link
Reference in a new issue