Skip to content

Commit 0a5a9c0

Browse files
Fix issue templates (#31)
1 parent 8023eb6 commit 0a5a9c0

File tree

5 files changed

+37
-20
lines changed

5 files changed

+37
-20
lines changed

.github/ISSUE_TEMPLATE/community-request.yaml renamed to .github/ISSUE_TEMPLATE/community-request-template.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,23 +7,28 @@ assignees: ''
77

88
---
99

10-
# Community Note
10+
## Community Note
11+
1112
* Please vote for this issue by adding a 👍 reaction to the issue. This will help the community and maintainers from the Amazon Chime SDK team to prioritize this request.
1213
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
1314
* Please go through the existing [issues](https://github.com/aws/amazon-chime-sdk-cpp/issues) to see if your request has already been recommended.
1415
* Please do not use this template for bugs or support.
1516
* If you are interested in working on this issue or have submitted a pull request, please leave a comment.
1617

17-
# Tell us about your request
18-
## Is this a request for the Amazon Chime SDK for C++, or with the Amazon Chime SDK for C++ Signaling Client?
18+
## Tell us about your request
19+
20+
### Is this a request for the Amazon Chime SDK for C++, or with the Amazon Chime SDK for C++ Signaling Client?
21+
22+
### What do you want us to build?
1923

20-
## What do you want us to build?
24+
### Tell us about the problem you are trying to solve and why is it hard?
2125

22-
## Tell us about the problem you are trying to solve and why is it hard?
2326
The more details you provide us, the better we will be able to help you.
2427

25-
## How are you currently solving a problem?
28+
### How are you currently solving a problem?
29+
2630
Are there any workarounds or mitigations you have used? Why is it not working for you?
2731

28-
## Additional context
32+
### Additional context
33+
2934
Anything else we should know?

.github/ISSUE_TEMPLATE/cpp-sdk-build-issue.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
name: Build Failure Report
2-
description: Report unexpected build failures with the project
1+
name: Amazon Chime SDK for C++ Build Failure Report
2+
description: Report unexpected build failures with the Amazon Chime SDK for C++
33
body:
44
- type: input
55
id: subproject
File renamed without changes.

.github/ISSUE_TEMPLATE/signaling-client-build-issue.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
name: Build Failure Report
2-
description: Report unexpected build failures with the project
1+
name: Signaling Client Build Failure Report
2+
description: Report unexpected build failures with the Amazon Chime SDK for C++ Signaling Client
33
body:
44
- type: input
55
id: subproject

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 21 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,30 @@
1-
**Issue #:**
21

3-
**Description of changes:**
2+
### Description of changes
43

5-
**Testing:**
6-
*Can these tested using the demo CLI? Please provide reproducible step-by-step instructions.*
4+
<!--- Provide a concise overview of the changes. -->
75

8-
**Checklist:**
6+
**Github Issue:**
97

10-
1. What platforms has this change been built on? What `cmake` commands were used to generate the build files?
8+
### Testing
119

12-
2. Does this change risk impacting platforms other then the one tested?
10+
<!-- Can these tested using the demo CLI? Please provide reproducible step-by-step instructions. -->
11+
12+
### Checklist
13+
14+
*What platforms has this change been built on? What `cmake` commands were used to generate the build files?*
15+
16+
17+
18+
*Does this change risk impacting platforms other then the one tested?*
19+
20+
21+
22+
*Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?*
23+
24+
25+
26+
*Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?*
1327

14-
3. Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
1528

16-
4. Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
1729

1830
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

0 commit comments

Comments
 (0)