I have my own, manual copy (not fork!) of the bangle.js github.
This is where I do all my crazy development stuff.
As soon as something is ready to be published, I copy the files over to my fork of the bangle.js github. Then I test if app installation is working as expected.
The I crate a pull request.
This way I keep the crazyness and too many commits out of the fork and out of the bangle.js github.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I have my own, manual copy (not fork!) of the bangle.js github.
This is where I do all my crazy development stuff.
As soon as something is ready to be published, I copy the files over to my fork of the bangle.js github. Then I test if app installation is working as expected.
The I crate a pull request.
This way I keep the crazyness and too many commits out of the fork and out of the bangle.js github.
No idea if there is a better way.
Example:
My bangle.js copy: https://github.com/Purple-Tentacle/BangleAppsDev
My bangle.js fork: https://github.com/Purple-Tentacle/BangleApps