mirror of
https://github.com/naimo84/awesome-nodered.git
synced 2026-04-29 18:18:39 -05:00
35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
# Contribution Guidelines
|
|
|
|
Please note that this project is released with a
|
|
[Contributor Code of Conduct](code-of-conduct.md). By participating in this
|
|
project you agree to abide by its terms.
|
|
|
|
---
|
|
|
|
Ensure your pull request adheres to the following guidelines:
|
|
|
|
- If you add a contrib node, it has more than 10 Stars.
|
|
- Search previous suggestions before making a new one, as yours may be a duplicate
|
|
- Use `Node-RED` casing
|
|
- If you just created something, wait at least a couple of weeks before submitting
|
|
- You should of course have read or used the thing you're submitting
|
|
- Make an individual pull request for each suggestion
|
|
- Use the following format: `[name](link) - Description`
|
|
- Keep descriptions short and simple, but descriptive
|
|
- Start the description with a capital
|
|
- Check your spelling and grammar
|
|
- Make sure your text editor is set to remove trailing whitespace
|
|
- Link additions should be added to the bottom of the relevant section
|
|
- New categories or improvements to the existing categorization are welcome
|
|
- Pull requests should have a useful title and include a link to the package and why it should be included
|
|
|
|
Thank you for your suggestion!
|
|
|
|
## Updating your PR
|
|
|
|
A lot of times, making a PR adhere to the standards above can be difficult.
|
|
If the maintainers notice anything that we'd like changed, we'll ask you to
|
|
edit your PR before we merge it. There's no need to open a new PR, just edit
|
|
the existing one. If you're not sure how to do that,
|
|
[here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
|
|
on the different ways you can update your PR so that we can merge it. |