Skip to content

Commit fb3082b

Browse files
committed
Updates issue templates to prevent segment information to show up in issue
1 parent 5269c95 commit fb3082b

File tree

2 files changed

+36
-15
lines changed

2 files changed

+36
-15
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

+23-9
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,30 @@ labels: bug
66
assignees: ''
77

88
---
9-
10-
**Are you in the right place?**
9+
<!--
10+
11+
Are you in the right place?
1112
- If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit.
1213
- If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask.
1314
- If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.*
1415
16+
-->
17+
1518
**Checklist**
1619
- Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image?
20+
- Yes / No
1721
- Are you sure you're not using someone else's docker image?
18-
- If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
22+
- Yes / No
23+
- Have you searched for similar issues (both open and closed)?
24+
- Yes / No
1925

2026
**Describe the bug**
21-
- A clear and concise description of what the bug is.
22-
- What version of Nginx Proxy Manager is reported on the login page?
27+
<!-- A clear and concise description of what the bug is. -->
28+
29+
30+
**Nginx Proxy Manager Version**
31+
<!-- What version of Nginx Proxy Manager is reported on the login page? -->
32+
2333

2434
**To Reproduce**
2535
Steps to reproduce the behavior:
@@ -28,14 +38,18 @@ Steps to reproduce the behavior:
2838
3. Scroll down to '....'
2939
4. See error
3040

41+
3142
**Expected behavior**
32-
A clear and concise description of what you expected to happen.
43+
<!-- A clear and concise description of what you expected to happen. -->
44+
3345

3446
**Screenshots**
35-
If applicable, add screenshots to help explain your problem.
47+
<!-- If applicable, add screenshots to help explain your problem. -->
48+
3649

3750
**Operating System**
38-
- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error.
51+
<!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. -->
52+
3953

4054
**Additional context**
41-
Add any other context about the problem here, docker version, browser version if applicable to the problem. Too much info is better than too little.
55+
<!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->

.github/ISSUE_TEMPLATE/feature_request.md

+13-6
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,26 @@ assignees: ''
77

88
---
99

10-
**Are you in the right place?**
10+
<!--
11+
12+
Are you in the right place?
1113
- If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit.
1214
- If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask.
13-
- If you have a feature request for NPM then you are in the *right place.*
15+
- If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.*
16+
17+
-->
1418

1519
**Is your feature request related to a problem? Please describe.**
16-
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
20+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
21+
1722

1823
**Describe the solution you'd like**
19-
A clear and concise description of what you want to happen.
24+
<!-- A clear and concise description of what you want to happen. -->
25+
2026

2127
**Describe alternatives you've considered**
22-
A clear and concise description of any alternative solutions or features you've considered.
28+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
29+
2330

2431
**Additional context**
25-
Add any other context or screenshots about the feature request here.
32+
<!-- Add any other context or screenshots about the feature request here. -->

0 commit comments

Comments
 (0)