mirror of
https://github.com/KjellKod/g3log.git
synced 2024-12-13 10:42:56 +01:00
Update issue templates
This commit is contained in:
parent
3d08371fc6
commit
d56589e649
6
.github/ISSUE_TEMPLATE/bug_report.md
vendored
6
.github/ISSUE_TEMPLATE/bug_report.md
vendored
@ -11,9 +11,9 @@ assignees: ''
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
**To Reproduce**
|
||||
What system, compiler etc was used to run this.
|
||||
Is something done differently on your setup than what the project specifies?
|
||||
Have you provided a code snippet that can be tested?
|
||||
- What system, compiler etc was used to run this?
|
||||
- Is something done differently on your setup than what the documentation specifies?
|
||||
- Have you provided a code snippet that can be tested?
|
||||
|
||||
**Additional context**
|
||||
Add any other context about the problem here.
|
||||
|
1
.github/ISSUE_TEMPLATE/feature_request.md
vendored
1
.github/ISSUE_TEMPLATE/feature_request.md
vendored
@ -9,6 +9,7 @@ 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 [...]
|
||||
Keep in mind that g3log is community driven. Do you want to take on the feature work yourself, or do you want someone else to take it on? The latter will require a whole lot more "selling". If you want to drive it yourself you can likely get community feedback on your idea + definitely great code reviews.
|
||||
|
||||
**Describe the solution you'd like**
|
||||
A clear and concise description of what you want to happen.
|
||||
|
Loading…
Reference in New Issue
Block a user