How to create the tree for creating a commit? about node-gitteh HOT 6 OPEN

@iamwilhelm This is something I hope to address in the short-term with a v0.18.0 release. Hang tight, or feel free to contribute if you're able! :)

from node-gitteh.

I had wanted to, actually. However, at the time, the repo was in the state where it didn't even compile (against node 0.6.12, and the docs didn't say which version I needed), so that was a high barrier of entry. In addition, you said you were refactoring at the time, so I wanted to wait til you were done.

It'd be easier for us to contribute in the future, if master always works, even if it's behind the edge! And make the refactorings on a different branch than master.

from node-gitteh.

@iamwilhelm Understood. The refactor was necessary for gitteh to continue living, as prior to the refactor the native bindings code was getting pretty complicated. I will endeavour to keep master more stable (got Travis building and testing master now for example), but bear in mind the stable release tags are what should generally be used though!

from node-gitteh.

@samcday So from now on, contribute by forking from the stable tags instead of master?

from node-gitteh.

@iamwilhelm I don't think that would be strictly necessary - you're better off creating a topic branch for contributions off whatever the latest HEAD of master is. Of course when it comes time to submit it upstream you'll want to rebase your changes on top of whatever new stuff is available, and this may introduce merge conflicts to be dealt with. That said I'm happy with where the codebase is at, and won't be making any crazy refactors that render your contributions-in-progress worthless or anything :)

from node-gitteh.

I really wanted this feature too, so I made a pull request. Please check out #63

from node-gitteh.