Skip to content

Commit 883b3de

Browse files
committed
Add Bug and Feature Request templates for repository
1 parent 50396f4 commit 883b3de

File tree

2 files changed

+99
-0
lines changed

2 files changed

+99
-0
lines changed
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
name: Bug Report
3+
about: Report a bug or unexpected behavior in DXClusterGoAPI
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
---
8+
9+
## Description
10+
11+
A clear and concise description of the bug.
12+
13+
## Steps to Reproduce
14+
15+
1.
16+
2.
17+
3.
18+
19+
## Expected Behavior
20+
21+
What you expected to happen.
22+
23+
## Actual Behavior
24+
25+
What actually happened.
26+
27+
## Environment
28+
29+
- **Go version** (if building from source):
30+
- **Deployment method**: <!-- Docker / binary / source -->
31+
- **OS / architecture**:
32+
- **DXClusterGoAPI version / commit**:
33+
34+
## Configuration
35+
36+
Relevant environment variables (redact any credentials):
37+
38+
```
39+
# Example — redact passwords and sensitive values
40+
CLUSTERS=dx.example.com:7300,cluster2.example.com:7300
41+
LOG_LEVEL=info
42+
POTA_ENABLED=true
43+
REDIS_ADDR=
44+
LOTW_ENABLED=false
45+
```
46+
47+
- Number of configured clusters:
48+
- POTA integration enabled: <!-- yes / no -->
49+
- LoTW integration enabled: <!-- yes / no -->
50+
- Redis/caching enabled: <!-- yes / no -->
51+
52+
## Logs
53+
54+
Relevant log output. If possible, reproduce with `LOG_LEVEL=debug`:
55+
56+
```
57+
paste logs here
58+
```
59+
60+
## Additional Context
61+
62+
Any other information that may help diagnose the issue (e.g. network topology, firewall rules, cluster software version).
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Feature Request
3+
about: Suggest a new feature or improvement for DXClusterGoAPI
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
---
8+
9+
## Problem / Motivation
10+
11+
What use case or gap does this feature address? Who would benefit and how?
12+
13+
## Proposed Solution
14+
15+
Describe the desired behavior or feature in detail.
16+
17+
## Alternatives Considered
18+
19+
What other approaches did you think about? Why do you prefer the proposed solution?
20+
21+
## Affected Components
22+
23+
Check all that apply:
24+
25+
- [ ] API endpoints
26+
- [ ] Cluster connection
27+
- [ ] POTA integration
28+
- [ ] DXCC enrichment
29+
- [ ] LoTW integration
30+
- [ ] Redis / caching
31+
- [ ] Configuration
32+
- [ ] Docker / deployment
33+
- [ ] Other:
34+
35+
## Additional Context
36+
37+
Mockups, examples, links to relevant specs or prior art, or any other context.

0 commit comments

Comments
 (0)