Skip to content
This repository was archived by the owner on Nov 1, 2025. It is now read-only.

Commit 2eb5d3e

Browse files
committed
add github bug report and feature request templates
1 parent b22fa8b commit 2eb5d3e

File tree

2 files changed

+60
-0
lines changed

2 files changed

+60
-0
lines changed
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
5+
---
6+
7+
### Prerequisites
8+
9+
* [ ] I am running the [latest version](https://github.com/dan-v/awslambdaproxy/releases) of awslambdaproxy
10+
* [ ] I am have read the [README](https://github.com/dan-v/awslambdaproxy#usage) instructions and the [FAQ](https://github.com/dan-v/awslambdaproxy#faq)
11+
12+
### Description
13+
14+
[Description of the issue]
15+
16+
### Steps to Reproduce
17+
18+
1. [First Step]
19+
2. [Second Step]
20+
3. [and so on...]
21+
22+
**Expected behavior:** [What you expected to happen]
23+
24+
**Actual behavior:** [What actually happened]
25+
26+
### Environment
27+
* If you are using CLI, get the version and specify the full command you are using.
28+
```
29+
./awslambdaproxy version
30+
awslambdaproxy version 0.0.12
31+
./awslambdaproxy -r us-west-2,us-west-1 -f 60
32+
```
33+
* If you are using Docker, get the version and specify the full command you are using.
34+
```
35+
docker run -it --rm --entrypoint /app/awslambdaproxy vdan/awslambdaproxy -v
36+
awslambdaproxy version 0.0.12
37+
docker run -d vdan/awslambdaproxy -r us-west-2,us-west-1 -f 60
38+
```
39+
40+
### Error Output
41+
```
42+
...
43+
```
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
**Is your feature request related to a problem? Please describe.**
8+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
9+
10+
**Describe the solution you'd like**
11+
A clear and concise description of what you want to happen.
12+
13+
**Describe alternatives you've considered**
14+
A clear and concise description of any alternative solutions or features you've considered.
15+
16+
**Additional context**
17+
Add any other context or screenshots about the feature request here.

0 commit comments

Comments
 (0)