Skip to content

Commit f70995e

Browse files
xBlaz3kxlorenzodonini
authored andcommitted
Added issue and pull request templates.
1 parent 717e26d commit f70995e

File tree

2 files changed

+72
-0
lines changed

2 files changed

+72
-0
lines changed

.github/ISSUE_TEMPLATE.md

+40
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
<!-- ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION. -->
2+
3+
**OCPP version:**
4+
[x] **1.6**
5+
[ ] **2.0.1**
6+
7+
**I'm submitting a ...**
8+
<!-- (check one with "x") -->
9+
[ ] bug report
10+
[ ] feature request
11+
12+
**Current behavior:**
13+
<!-- Describe how the bug manifests. -->
14+
15+
**Expected behavior:**
16+
<!-- Describe what the behavior would be without the bug. -->
17+
18+
**Steps to reproduce:**
19+
<!-- Please explain the steps required to duplicate the issue, especially if you are able to provide a sample application. -->
20+
21+
**Related code:**
22+
23+
<!-- If you are able to illustrate the bug or feature request with an example, please provide a sample application via one of the following means:
24+
25+
A sample application via GitHub
26+
27+
StackBlitz (https://stackblitz.com)
28+
29+
-->
30+
31+
```
32+
insert short code snippets here
33+
```
34+
35+
**Other information:**
36+
<!-- List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, etc. -->
37+
38+
```
39+
insert the output here
40+
```

.github/pull_request_template.md

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
## Proposed changes
2+
3+
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
4+
If it fixes a bug or resolves a feature request, be sure to link to that issue.
5+
6+
## Types of changes
7+
8+
What types of changes does your code introduce?
9+
_Put an `x` in the boxes that apply_
10+
11+
- [ ] Bugfix (non-breaking change which fixes an issue)
12+
- [ ] New feature (non-breaking change which adds functionality)
13+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
14+
- [ ] Documentation Update (if none of the other choices apply)
15+
16+
## Checklist
17+
18+
_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
19+
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
20+
merging your code._
21+
22+
- [ ] I have read the [CONTRIBUTING](https://github.com/xBlaz3kx/ocppManager-go/blob/master/CONTRIBUTING.md) doc
23+
- [ ] I have signed the CLA
24+
- [ ] Lint and unit tests pass locally with my changes
25+
- [ ] I have added tests that prove my fix is effective or that my feature works
26+
- [ ] I have added necessary documentation (if appropriate)
27+
- [ ] Any dependent changes have been merged and published in downstream modules
28+
29+
## Further comments
30+
31+
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
32+
did and what alternatives you considered, etc...

0 commit comments

Comments
 (0)