Skip to content

Commit 80745a7

Browse files
authored
Create pull_request_template.md
1 parent 0d28c1a commit 80745a7

1 file changed

Lines changed: 50 additions & 0 deletions

File tree

.github/pull_request_template.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
## 🚀 Description, Motivation, and Context
2+
<!--
3+
Describe your changes in detail. Why is this change required? What problem does it solve?
4+
Provide any additional context on complex decisions that were made and try to preemptively
5+
answer questions that you know will arise for reviewers.
6+
-->
7+
## 📖 Issues and Related PRs
8+
<!-- Add the Issue URL here that matches the issue used in the PR title -->
9+
- **Issue Url:** (https://github.com/WebexCommunity/webex-go-sdk/issues/000)
10+
<!--
11+
Link any additional related JIRA issues, Github issues, SCAVA vuln, or related Pull Requests.
12+
If the PR closes any open PRs or issues, use [closing words](https://help.github.com/articles/closing-issues-via-commit-messages/)
13+
followed by the ticket number fixed by this PR
14+
Examples:
15+
- **CDETS issue:** [CSCvy12345](https://cdetsng.cisco.com/summary/#/defect/CSCvy12345)
16+
- **Github issue:** #0, Closes #1, Closes #5
17+
- **JIRA ticket:** (https://cisco-jira.atlassian.net/browse/CXC-123)
18+
- **Followup JIRA tickets for issues unaddressed in this changeset:**
19+
- **Related PR:** #123
20+
-->
21+
## 🖼 Screenshots
22+
<!--
23+
Screenshots of your change are helpful to reviewers and stakeholders,
24+
in order to locate your change in the UI and do a quick visual check.
25+
Feel free to include graphs and charts,
26+
for example before and after changes that improve performance.
27+
If this does not require UI changes, feel free to exclude.
28+
-->
29+
## 🌮 How This Was Tested
30+
<!--
31+
Please check all that apply (at least one should always be selected).
32+
Provide any additional context that would be helpful for reviewers,
33+
including specific steps to reproduce/test.
34+
-->
35+
- [ ] Ran locally and verified
36+
- [ ] Created tests (unit and/or E2E)
37+
- [ ] Automated testing unnecessary (chores, doc updates, etc.)
38+
## Required Items Complete:
39+
- [ ] Unit tests written
40+
- [ ] Integration tests written
41+
- [ ] Coverage verified
42+
- [ ] Functionally tested
43+
- [ ] Deployable to production
44+
- [ ] Uses feature flags <List of flag names>
45+
- [ ] README updated
46+
- [ ] Build passes
47+
Security:
48+
<! --
49+
Fill out this section if you are addressing a security feature/issue. Describe the feature/issue.
50+
-->

0 commit comments

Comments
 (0)