Skip to content

Commit 059099f

Browse files
hasufellBodigrim
andauthored
Add issue templates (#236)
* Add issue templates * Update .github/ISSUE_TEMPLATE/bug_report.md Co-authored-by: ˌbodʲɪˈɡrʲim <[email protected]> Co-authored-by: ˌbodʲɪˈɡrʲim <[email protected]>
1 parent 43acabe commit 059099f

File tree

2 files changed

+73
-0
lines changed

2 files changed

+73
-0
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: 'status: needs triage, type: bug'
6+
assignees: ''
7+
8+
---
9+
10+
<!--
11+
When filing an issue, please fill out as much of the information below as you can.
12+
This helps us to debug your issue, but is not required!
13+
-->
14+
15+
### Your environment
16+
17+
Which OS do you use:
18+
<!-- MacOS, Ubuntu, ArchLinux, etc... -->
19+
Describe your project (alternative: link to the project):
20+
<!-- stack.yaml, package.yaml, *.cabal files, cabal.project -->
21+
22+
### Steps to reproduce
23+
<!-- Tell us how to reproduce this issue. -->
24+
25+
### Expected behaviour
26+
<!-- Tell us what should happen. -->
27+
28+
### Actual behaviour
29+
<!-- Tell us what happens instead. -->
30+
31+
### Include debug information
32+
33+
<!-- Include any useful debug information, such as your 'HsUnixConfig.h' file (usually found inside 'dist-newstyle/') -->
34+
35+
### API breaking changes
36+
37+
<!-- If a bugfix causes API breaking changes, consider whether there's a solution without breaking API. -->
38+
39+
### Posix compliance
40+
41+
<!-- Research about relevant parts of the POSIX spec: https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/ -->
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Feature request
3+
about: Suggest an enhancement to the package
4+
title: ''
5+
labels: 'status: needs triage, type: enhancement'
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
12+
<!-- A clear and concise description of what the problem is -->
13+
14+
**Describe the solution you'd like**
15+
16+
<!-- A clear and concise description of what you want to happen. -->
17+
18+
**Describe alternatives you've considered**
19+
20+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
21+
22+
**Additional context**
23+
24+
<!-- Add any other context about the feature request here. -->
25+
26+
**API breaking changes**
27+
28+
<!-- If this feature causes API breaking changes, explain why it's worth it. -->
29+
30+
**Posix compliance**
31+
32+
<!-- Research about relevant parts of the POSIX spec: https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/ -->

0 commit comments

Comments
 (0)