Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
Comment on lines +4 to +5
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To improve issue triaging, consider pre-filling the title prefix and labels. This helps automatically categorize new issues. For example, you could set a title prefix for bugs and automatically apply a 'bug' label.

Suggested change
title: ''
labels: ''
title: '[BUG] '
labels: 'bug'

assignees: ''

---

Expand All @@ -19,4 +22,4 @@ about: Create a report to help us improve
## Specifications

- Version:
- Platform:
- Platform:
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ''
Comment on lines +4 to +5
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To streamline issue management, you could pre-fill the title with a prefix and automatically add a relevant label. For instance, using a '[FEAT]' prefix and an 'enhancement' label can help quickly identify feature requests.

Suggested change
title: ''
labels: ''
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