Native GitFlow Libgit2sharp

[jzoss]

Hi, this is not an issue, but I was not sure the best way to contact you.. So I am the developer for a git plugin for VS 2015. One of the feature requests was to add GitFlow to my plugin. I saw your code and thought is looked great, but I just spent a lot of time getting rid of all the command line calls.. so I figured why not make a wrapper for libgit2sharp to do all the work.. Then I don't have to install the GitFlow Extensions project. Anyway.. I started the project here but stealing a bit of your fine code. Just wanted to say thanks. and say, if you are interested in help.. that would be awesome, or if you just want to use it in your project when you are done.. also awesome. Even if you don't do either .. just wanted to let you know..say thanks for helping me get started!

Have a good day..

[jakobehn]

Thanks for letting me know, wish you good luck with the extension!

I have definitely though about implementing the gitflow logic myself, but since there seem to be quite a lot of activity on the AVH fork of git-flow, I think tagging along with that is also a good option.

[jzoss]

Cool.. I had not even seen that one.. So you would suggest that if we wanted to mirror a set of features .. The AVH git-flow is what you would suggest?

[jakobehn]

Well, I guess it's a matter of how much functionality you want to write yourself :-) It is definitely more complicated to integrate, compared to using an API like LigGit2Sharp. I've had issues with handling authentication, since the way the gitflow scripts prompts for credentials makes it very hard to catch this.

[jzoss]

Well I will start off slow. My idea right now is to do a functional copy.. So I mean I will start off slow.. working on getting the original git-flow commands. They are just wrappers for a few native git commands anyway.. So I was thinking I would just wrap the same native git commands.. For example the init function does it all through libgit2sharp using the config.set .. setting up the configs and all that... It's to get around the issues like you said with authentication or whatever. So what operation you had issues with should be much easier since I am not ever talking to the command line. The limitation would be libgit2sharp.. If there was something it did not support .. that would be an issue.

[yannduran]

@jzoss I think it's a great idea to have a managed code wrapper for the native gitflow commands!