Skip to content

Commit e4c4553

Browse files
authored
Merge pull request #504 from andyzhangx/template
doc: add issue and PR templates
2 parents 150c9d9 + bf4af0e commit e4c4553

File tree

4 files changed

+68
-0
lines changed

4 files changed

+68
-0
lines changed

Diff for: .github/ISSUE_TEMPLATE/bug-report.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve this project
4+
5+
---
6+
7+
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
8+
-->
9+
10+
11+
**What happened**:
12+
13+
**What you expected to happen**:
14+
15+
**How to reproduce it**:
16+
17+
**Anything else we need to know?**:
18+
19+
**Environment**:
20+
- CSI Spec version:
21+
- Others:

Diff for: .github/ISSUE_TEMPLATE/enhancement.md

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: Enhancement Request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
8+
**Is your feature request related to a problem?/Why is this needed**
9+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
10+
11+
**Describe the solution you'd like in detail**
12+
<!-- A clear and concise description of what you want to happen. -->
13+
14+
**Describe alternatives you've considered**
15+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
16+
17+
**Additional context**
18+
<!-- Add any other context or screenshots about the feature request here. -->

Diff for: .github/ISSUE_TEMPLATE/support.md

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
name: Support Request
3+
about: Ask questions about this project
4+
5+
---
6+

Diff for: .github/PULL_REQUEST_TEMPLATE.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
**What type of PR is this?**
2+
3+
**What this PR does / why we need it**:
4+
5+
**Which issue(s) this PR fixes**:
6+
<!--
7+
*Automatically closes linked issue when PR is merged.
8+
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
9+
_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
10+
-->
11+
Fixes #
12+
13+
**Special notes for your reviewer**:
14+
15+
**Does this PR introduce an API-breaking change?**:
16+
<!--
17+
If no, just write "NONE" in the release-note block below.
18+
If yes, a release note is required:
19+
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
20+
-->
21+
```release-note
22+
none
23+
```

0 commit comments

Comments
 (0)