I’m pleased to announce the new package GitCommand.jl.
GitCommand allows you to use command-line Git in your Julia packages. You do not need to have Git installed on your computer, and neither do the users of your packages!
Should this perhaps replace Git.jl? The latter has a premium name but is barely maintained. AFAIR it’s old git functionality that has been in Base at some point (please correct me if I’m wrong here).
Also, could someone point out in which cases one should use this (i.e. full git) rather than the LibGit2 stdlib? I guess I’m only asking what the limitiations of LibGit2 are compared to regular git.
For anybody who has the same minor problem of additional output at the end of a git call:
Calling e.g.
julia> run(git`status`)
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
Process(setenv(`'C:\Users\oheil\.julia\artifacts\08d6d8573a69feabe698828070d44081361f4bcd\bin\git.exe' status`,[...
LONG ANNOYING ENVIRONMENT HERE
...]), ProcessExited(0))
it can easily be suppressed by a trainling ; :
julia> run(git`status`);
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
julia>
Thanks again to OP, who pointed this triviality out to me, after I opened an issue about it
I am doubling this question. We use LibGit2 quite heavily in DrWatson. So the question is, what are the reasons for us to switch to this new package (if any)?