Skip to content

Commit e9a026c

Browse files
committed
Add issue/pr templates
1 parent cb4f46d commit e9a026c

2 files changed

Lines changed: 65 additions & 0 deletions

File tree

.github/ISSUE_TEMPLATE.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
## Before you hit that Submit button....
2+
3+
This issue tracker is for problems with the Node-RED runtime, the editor or the
4+
core nodes.
5+
6+
If your issue is:
7+
8+
- a general 'how-to' type question,
9+
- a feature request or suggestion for a change,
10+
- or problems with 3rd party (`node-red-contrib-`) nodes
11+
12+
please use the
13+
[mailing list](https://groups.google.com/forum/#!forum/node-red),
14+
[slack team](https://nodered.org/slack) or ask a question on [Stack Overflow](https://stackoverflow.com/questions/tagged/node-red) and tag it `node-red`.
15+
16+
That way the whole Node-RED user community can help, rather than rely on the core development team.
17+
18+
## So you have a real issue to raise...
19+
20+
To help us understand the issue, please fill-in as much of the following information
21+
as you can:
22+
23+
### What are the steps to reproduce?
24+
25+
### What happens?
26+
27+
### What do you expect to happen?
28+
29+
### Please tell us about your environment:
30+
31+
- [ ] Node-RED version:
32+
- [ ] node.js version:
33+
- [ ] npm version:
34+
- [ ] Platform/OS:
35+
- [ ] Browser:

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
## Before you hit that Submit button....
2+
3+
Please read our [contribution guidelines](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
4+
before submitting a pull-request.
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+
14+
If you want to raise a pull-request with a new feature, or a refactoring
15+
of existing code, it **may well get rejected** if it hasn't been discussed on
16+
the [mailing list](https://groups.google.com/forum/#!forum/node-red) or
17+
[slack team](https://nodered.org/slack) first.
18+
19+
20+
## Proposed changes
21+
22+
Describe the nature of this change. What problem does it address?
23+
24+
## Checklist
25+
_Put an `x` in the boxes that apply_
26+
27+
- [ ] I have read the [contribution guidelines](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
28+
- [ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
29+
- [ ] I have run `grunt` to verify the unit tests pass
30+
- [ ] I have added suitable unit tests to cover the new/changed functionality

0 commit comments

Comments
 (0)