Skip to content

Commit 70fd0c1

Browse files
Add issue and PR templates (sindresorhus#353)
Fixes sindresorhus#352 Co-authored-by: Sindre Sorhus <sindresorhus@gmail.com>
1 parent e8a3a7d commit 70fd0c1

File tree

3 files changed

+63
-0
lines changed

3 files changed

+63
-0
lines changed
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve np
4+
---
5+
6+
<!--- Provide a short summary of the issue in the title above -->
7+
8+
## Description
9+
10+
<!-- Write a clear and concise description of what the issue is -->
11+
12+
## Steps to reproduce
13+
14+
<!--- Let us how how we can reproduce the issue on our end -->
15+
16+
1.
17+
2.
18+
3.
19+
20+
## Expected behavior
21+
22+
<!--- Tell us what you expected to happen -->
23+
24+
## Environment
25+
26+
<!-- Mention which versions of np, Node.js, npm and Git you're using, as well as your OS and version -->
27+
28+
np - x.x.x
29+
Node.js - x.x.x
30+
npm - x.x.x
31+
Git - x.x.x
32+
OS - XXX x.x.x
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea
4+
---
5+
6+
<!--- Provide a short summary of the request in the title above -->
7+
8+
## Description
9+
10+
<!-- Write a clear and concise description of the feature -->
11+
12+
**Is the feature request related to a problem?**
13+
14+
<!-- Describe what the problem is (e.g. I'm always frustrated when […]) -->
15+
16+
## Possible solution
17+
18+
<!-- If possible, let us know how you think the feature should be implemented -->
19+
20+
## Alternatives
21+
22+
<!-- Include any alternative solutions and features you've considered -->

.github/pull_request_template.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
<!--
2+
3+
Thanks for submitting a pull request 🙌
4+
5+
**Note:** Please don't create a pull request which has significant changes (i.e. adds new functionality or modifies existing one in a non-trivial way) without creating an issue first.
6+
7+
Try to limit the scope of your pull request and provide a general description of the changes. If this fixes an open issue, link to it in the following way: `Fixes #321`. New features and bug fixes should come with tests.
8+
9+
-->

0 commit comments

Comments
 (0)