forked from node-red/node-red-ui-nodes
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of https://github.com/node-red/node-red-ui-nodes
- Loading branch information
Showing
2 changed files
with
68 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
<!-- | ||
## Before you hit that Submit button.... | ||
This issue tracker is for problems with the extra UI nodes maintained by the Node-RED project. | ||
If your issue is: | ||
- a general 'how-to' type question, | ||
- a feature request or suggestion for a change, | ||
- or problems with 3rd party (`node-red-contrib-`) nodes | ||
please use the [Node-RED Forum](https://discourse.nodered.org) or [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`. | ||
That way the whole Node-RED user community can help, rather than rely on the core development team. | ||
## So you have a real issue to raise... | ||
To help us understand the issue, please fill-in as much of the following information as you can: | ||
--> | ||
|
||
### Which node are you reporting an issue on? | ||
|
||
### What are the steps to reproduce? | ||
|
||
### What happens? | ||
|
||
### What do you expect to happen? | ||
|
||
### Please tell us about your environment: | ||
|
||
- [ ] Node-RED version: | ||
- [ ] node.js version: | ||
- [ ] npm version: | ||
- [ ] Platform/OS: | ||
- [ ] Browser: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
<!-- | ||
## Before you hit that Submit button.... | ||
Please read our [contribution guidelines](https://github.com/node-red/node-red-nodes/blob/master/CONTRIBUTING.md) | ||
before submitting a pull-request. | ||
## Types of changes | ||
What types of changes does your code introduce? | ||
Put an `x` in the boxes that apply | ||
--> | ||
|
||
- [ ] Bugfix (non-breaking change which fixes an issue) | ||
- [ ] New feature (non-breaking change which adds functionality) | ||
|
||
<!-- | ||
If you want to raise a pull-request with a new feature, or a refactoring | ||
of existing code, it **may well get rejected** if it hasn't been discussed on | ||
the [forum](https://discourse.nodered.org) or | ||
[slack team](https://nodered.org/slack) first. | ||
--> | ||
|
||
## Proposed changes | ||
|
||
<!-- Describe the nature of this change. What problem does it address? --> | ||
|
||
## Checklist | ||
<!-- Put an `x` in the boxes that apply --> | ||
|
||
- [ ] I have read the [contribution guidelines](https://github.com/node-red/node-red-nodes/blob/master/CONTRIBUTING.md) | ||
- [ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team. | ||
- [ ] I have run `grunt` to verify the unit tests pass | ||
- [ ] I have added suitable unit tests to cover the new/changed functionality |