# Developing on fork of node

**URL:** <https://discourse.nodered.org/t/developing-on-fork-of-node/18927>\
**Category:** Developing Nodes\
**Created:** [8 December 2019 21:11 UTC](https://discourse.nodered.org/t/developing-on-fork-of-node/18927 "2019-12-08T21:11:38Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [8 December 2019 22:00 UTC](https://discourse.nodered.org/t/developing-on-fork-of-node/18927/11 "2019-12-08T22:00:57Z")

</div>

Someone who knows more than me told me to fork and then make a new branch in your fork and make the changes in that.

Then, when making a pull-request - you do it from your new branch - it keeps things cleaner I was told

While developing, I recommend just working on the node files in an alternate install from @TotallyInformation

> [@New Utility: alternate-node-red-installer](https://discourse.nodered.org/t/new-utility-alternate-node-red-installer/13490):
>
> Hi all, as I'm needing to install some clean installations of Node-RED for testing, I thought that I would finally get round to writing a proper tool for installing multiple independent instances of Node-RED. I've just finished that off and published to GitHub and npm so you should be able to use it straight away if you have a need for such a thing. It gives you a command-line installer that takes a single parameter controlling the root folder for installation. It should work on all platforms. …

Once I'm happy with changes - I then just copy/paste from local files into the github branch created earlier

---

_[View the full topic](https://discourse.nodered.org/t/developing-on-fork-of-node/18927)._