Skip to content

Commit 09ee818

Browse files
authored
chore: Add issue templates
1 parent f5c0be3 commit 09ee818

File tree

2 files changed

+61
-0
lines changed

2 files changed

+61
-0
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: bug, triage
6+
assignees: ''
7+
8+
---
9+
10+
**Previous issues**
11+
Have you searched the issue tracker to ensure this hasn't been discussed before?
12+
13+
**Version information:**
14+
- OS: (e.g. MacOS ARM, Windows x64)
15+
- PactNet Version:
16+
- .Net Version:
17+
- Pact Broker Version (if applicable):
18+
19+
**Describe the bug**
20+
A clear and concise description of what the bug is.
21+
22+
**Steps To Reproduce**
23+
Steps to reproduce the issue, including code snippets or preferably a link to a repository which reproduces the issue.
24+
25+
**Expected behavior**
26+
A clear and concise description of what you expected to happen.
27+
28+
**Log Output**
29+
Applicable log output. Please ensure you remove any sensitive information.
30+
31+
**Additional context**
32+
Add any other context about the problem here.
+29
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: 'RFC: <title>'
5+
labels: triage
6+
assignees: ''
7+
8+
---
9+
10+
**Previous issues**
11+
Have you searched the issue tracker to ensure this hasn't been discussed before?
12+
13+
**Is your feature request related to a problem? Please describe.**
14+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
15+
16+
**Describe the solution you'd like**
17+
A clear and concise description of what you want to happen.
18+
19+
**Breaking Changes**
20+
Does your proposed change include anything which would require a major version bump? If so, please detail them here. Please read the SemVer spec if you are unsure what this means.
21+
22+
**Potential Downsides/Caveats**
23+
A clear and concise description of any downsides or caveats your change would introduce.
24+
25+
**Describe alternatives you've considered**
26+
A clear and concise description of any alternative solutions or features you've considered.
27+
28+
**Additional context**
29+
Add any other context or screenshots about the feature request here.

0 commit comments

Comments
 (0)