-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide option to use command line Git instead of Cake.Git #183
Comments
Wouldn't it be more prudent to create a |
Yes, thought about this. What would be nice is to have an abstraction layer, which is then either implemented using LibGit2Sharp or by calling the command line client. If done across multiple addins, this would mean that we need a Cake.GitInterface addin, defining the interface and one addin implementing the interface for LibGit2Sharp and one for command line client. In the build you then would need to add the interface addin plus one of the implementation addins and register it. This is basically how extensibility is also handled in Cake.Issues, but in this case it probably would be easier to handle all this in a single addin which provides both possibilities. |
Created issue in cake-contrib/Cake_Git#146 for discussing this further |
For the time being, I decided to add an option to Cake.Issues recipe, which can be used to decide it Cake.Git or Git CLI should be used, as there are only 3 calls which are required. |
Cake.Git addin, which uses LibGit2Sharp, can have issues on certain environments. There should be an option which allows to use Cake.Issues.Recipe without Cake.Git but calls to Git command line instead.
The text was updated successfully, but these errors were encountered: