Skip to content

Commit c812e45

Browse files
committed
Fix PR template name
1 parent 3bf8f78 commit c812e45

File tree

1 file changed

+58
-0
lines changed

1 file changed

+58
-0
lines changed

.github/pull_request_template.md

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
<!-- Thanks for sending a pull request! Here are some tips for you:
2+
3+
1. If this is your first time, please read our contributor guidelines: https://github.com/tmobile/magtape/blob/master/CONTRIBUTING.md
4+
2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request.
5+
3. Ensure you have added and/or ran the appropriate tests for your PR
6+
4. If the PR is unfinished, please mark it as "[WIP]"
7+
-->
8+
9+
**What type of PR is this?**
10+
> Uncomment only one ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespace from that line:
11+
>
12+
> /kind bug
13+
> /kind cleanup
14+
> /kind deprecation
15+
> /kind design
16+
> /kind documentation
17+
> /kind feature
18+
19+
**What this PR does / why we need it**:
20+
21+
**Which issue(s) this PR fixes**:
22+
<!--
23+
*Automatically closes linked issue when PR is merged.
24+
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
25+
-->
26+
Fixes #
27+
28+
**Special notes for your reviewer**:
29+
30+
**Does this PR introduce a user-facing change?**:
31+
<!--
32+
If no, just write "NONE" in the release-note block below.
33+
If yes, a release note is required:
34+
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"
35+
-->
36+
37+
```release-note
38+
39+
```
40+
41+
**Additional documentation e.g., usage docs, etc.**:
42+
<!--
43+
This section can be blank if this pull request does not require a release note.
44+
45+
When adding links which point to resources within git repositories, like supporting documentation, please reference a specific commit and avoid
46+
linking directly to the master branch. This ensures that links reference a
47+
specific point in time, rather than a document that may change over time.
48+
49+
See here for guidance on getting permanent links to files: https://help.github.com/en/articles/getting-permanent-links-to-files
50+
51+
Please use the following format for linking documentation:
52+
- [Usage]: <link>
53+
- [Other doc]: <link>
54+
-->
55+
56+
```docs
57+
58+
```

0 commit comments

Comments
 (0)