3 ms·
Anyone know why this project encourages using a private fork to do contributing development? > "Make a public fork of Huginn. [...] Make a private, empty GitHu
by alxndr 13y ago
Anyone know why this project encourages using a private fork to do contributing development?
> "Make a public fork of Huginn. [...] Make a private, empty GitHub repository called huginn-private. Duplicate your public fork into your new private repository[. ...] Checkout your new private repository. Add your Huginn public fork as a remote to your new private repository[. ...] When you want to contribute patches, do a remote push from your private repository to your public fork of the relevant commits, then make a pull request to this repository."
- tectonic 13y agoJust to let you keep any private changes private. Perhaps it's not the best recommendation.
- alxndr 13y agoAh. It seems unnecessarily complicated for people trying to get started. Perhaps preface it with a note saying something like "if you'd like to keep your commits private, follow this brief guide" so it doesn't seem required?
- tectonic 13y agoI agree, thanks for pointing this out. I've extracted that section to the wiki.
- alxndr 13y agoNice! (For the record I can't wait to try out Huginn; I've been using Yahoo Pipes for years... I've apparently got one pipe from before when they started using only hex characters as pipe IDs.)