frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity
Page: Contribution Process
Pages
API Reference Architecture Overview Architecture: Cluster Multi Process Contribution Process Dashboard layout tool Definitions Deprecated: Message properties overriding set node properties Design Notes Design: dynamic palette Design: API Token management Design: CLI tool to produce a node skeleton Design: Concurrent editing Design: Custom Node admin route handling Design: Dynamic MQTT node Design: Dynamic node's icon Design: Editable port labels Design: Editor Events Design: Editor Themes Design: Editor UI Customisation Design: Encryption of credentials Design: Enhancements to Split Join nodes Design: Flow Linter Design: Flow Manipulation API Design: Flow file format v2 Design: Function Library node Design: Library Sidebar Design: Logging Framework Design: Node Generator Design: Node Messaging API Design: Node blacklist whitelist function Design: Node module lifecycle Design: Node settings Design: Palette Management UI Design: Persistable Context Design: Platform Specific Nodes Design: Projects Design: Runnable Project Design: Runtime Editor Split Design: Runtime Events Design: Runtime extension points Design: Subflow Enhancements Design: Subflow Instance properties Design: Subflow Node modules Design: Usage telemetry Design: Using environment variables Design: Version Control Design: adminAuth User Management Design: external file for function and templates nodes Design: i18n de Design: i18n Design: msg.parts description of usage Design: multiuser Design: subflows vNext Design: subflows Design:Shared Global Context Editor Mouse Actions Editor Runtime API Flow Format Flow testing Home Input node feature definitions Live runtime information Node Design Guidelines Node documentation guide Node msg Conventions Output node feature definitions Pluggable Message Routing Query node feature definitions ReadMe Raspberry Pi Advanced Runtime Editor Comms protocol Technical Interchange 2018 04 13 Technical Interchange Meetings Testing UI testing Watch node feature definitions Web Nodes outline adminAuth Credential Authentication dynamic palette join in auto mode npm installable nodes
2 Contribution Process
Nick O'Leary edited this page 2017-02-28 10:47:31 +00:00
Table of Contents

Git Workflow

  • master - this branch contains the latest shipped release of node-red, plus any additional bug fixes that have been made since. At any time, this branch could get shipped as the next maintenance release. At the time of writing, this contains 0.16.2 and a few fixes that will be released as 0.16.3 at some point.
  • Development branch (eg 0.17) - development work on the next milestone release occurs in a branch named after the expected release version number. This is where new features are developed. At the time of writing, this is the 0.17 release.
  • Larger features get developed in their own branches and merged to the current development branch as and when the feature is sufficiently stable for wider consumption.

Raising a pull-request

Code contributions arrive as pull requests. They should target the appropriate branch - bug fixes on released code to master, new features to the current development branch.

There are a lot of good guides to working with pull requests and we won't try to recreate them here. But the basic process is:

  1. Fork the repository you want to make a change on
  2. Create a branch on your fork for the changes
  3. Run the tests!
  4. Create a pull request to the upstream repository. Make sure you target the appropriate branch of the upstream repository. If you want, you can choose to allow us to commit changes to your branch - that may be useful if there are some changes needed on top of your code and we're in a position to help make them.

Once the PR is raised, we'll review the changes and provide feedback. If all looks good, we'll get it merged. Otherwise we may request some changes or decide the PR isn't suitable to merge. Either way, we'll discuss it via the PR.