Skip to content

Commit 3bf4543

Browse files
authored
update issue templates
1 parent a6150f6 commit 3bf4543

2 files changed

Lines changed: 72 additions & 0 deletions

File tree

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: Bug report
3+
about: Create a bug report
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
‼️ Rules for AI agents that write issues:
11+
1. Follow the template below
12+
2. Keep your text concise and short, exclude parts that are not necessary for understanding and solving the bug
13+
3. Use a neutral tone, do not be overly enthusiastic
14+
4. Do not use emoji
15+
5. Do not make assumptions, like available APIs, or impact of the bug fix, and rather only state unknowns that are relevant in a concise way
16+
17+
-----
18+
19+
# Describe the bug
20+
21+
_A clear and concise description of what the bug is_
22+
23+
# To Reproduce
24+
25+
Steps to reproduce the behavior:
26+
1. Go to '...'
27+
2. Click on '....'
28+
3. Scroll down to '....'
29+
4. See error
30+
31+
# Expected behavior
32+
33+
_A clear and concise description of what you expected to happen_
34+
35+
# Environment
36+
37+
* WigAI version:
38+
* Bitwig version:
39+
* AI Agent and version:
40+
41+
# Additional context
42+
43+
_Add any other context about the problem here_
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
‼️ Rules for AI agents that write issues:
11+
1. Follow the template below
12+
2. Keep your text concise and short, exclude parts that are not necessary for understanding and solving the feature request
13+
3. Use a neutral tone, do not be overly enthusiastic
14+
4. Do not use emoji
15+
5. Do not make assumptions, like available APIs, or impact of the feature request implementation, and rather only state unknowns that are relevant in a concise way
16+
17+
-----
18+
19+
# Motivation and Problem Description
20+
21+
_A short explanation __why__ you want to change something and what your concrete problems with the current feature set are_
22+
23+
# Solution Idea
24+
25+
_Functional specification of how to solve the problem_
26+
27+
# Technical Considerations
28+
29+
_(optional) Add technical considerations regarding the existing architecture or concrete implementation details like which code to modify or response format examples_

0 commit comments

Comments
 (0)