Skip to content

Commit ae573d0

Browse files
Add Generic Issue Templates (#136)
* Create generic_template * Rename generic_template to generic_template.md
1 parent 623f0f7 commit ae573d0

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed
+45
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
name: Generic Issue Template
3+
about: A general template for submitting issues
4+
title: "[ISSUE]"
5+
labels: ''
6+
assignees: ''
7+
---
8+
9+
### **Title**:
10+
_A clear, concise summary of the issue or task (what resolving it will accomplish in one sentence)._
11+
12+
---
13+
14+
### **Description**:
15+
_Why is this issue important? Provide context on the problem or enhancement, including any relevant background or discussions._
16+
17+
---
18+
19+
### **Where Should This Be Applied?**:
20+
_Indicate where this change should be implemented or documented (e.g., internal documentation, website, or specific files). If possible, specify the exact files or locations._
21+
22+
---
23+
24+
### **System Information (if applicable)**:
25+
_Provide any relevant system information, such as software versions (Python version, operating system, etc.), if necessary to understand the issue._
26+
27+
---
28+
29+
### **Steps to Reproduce (if applicable)**:
30+
_Step-by-step instructions on how to replicate the issue, if it's a bug or technical issue._
31+
32+
---
33+
34+
### **Proposed Fix (if known)**:
35+
_If you have an idea of how to resolve the issue, provide it here. This can include possible solutions or suggestions for improvement._
36+
37+
---
38+
39+
### **Additional Context**:
40+
_Add any extra details, references, links, or screenshots that may help in understanding or resolving the issue._
41+
42+
---
43+
44+
### **Task Label**:
45+
_Specify a label or category for the issue (e.g., bug, enhancement, task)._

0 commit comments

Comments
 (0)