Update gitexec to v2.0.1

[XhmikosR]

Currently, this breaks Windows testing. More specifically this patch: rvagg/gitexec@51ad38d

This PR is split from #61 so that we tackle the Windows issue separately.

Closes #54

[XhmikosR]

@rvagg: this is clearly broken and we need to fix it, why approve it :P

[XhmikosR]

Alright, after seeing the source code, I don't think changelog-maker can ever work on Windows native cmd...

I'm not sure how to make all of those posix stuff work on Windows like

$(git show -s --format=%cd `{{refcmd}}`)

2> /dev/null could probably be 2>NUL on Windows and it should work.

So, if after spending some time @rvagg you don't think we can make it work nice on Windows native cmd, we should revert the gitexec shell change and release 2.0.1 and then update to 2.0.1 here.

We'll just need to list that changelog-maker requires bash.

I managed to test the master branch on my Windows VM with msys2

xmr@DESKTOP-2989SN9 MSYS /c/Users/xmr/Desktop/changelog-maker
$ npm run unit

> [email protected] unit C:\Users\xmr\Desktop\changelog-maker
> tape test.js

TAP version 13
# test basic commit block
ok 1 should be equal
# test filter-release
ok 2 should be equal
# test simple
ok 3 should be equal
# test group, semver labels, PR-URL
ok 4 should be equal
# test simple group, semver labels, PR-URL
ok 5 should be equal
# test blank commit-url
ok 6 should be equal
# test blank commit-url
ok 7 should be equal

1..7
# tests 7
# pass  7

# ok

[XhmikosR]

Unless, we split the subcommands and we joined them thus skipping backticks and ${}. The rest should work fine.

It might be doable.

[rvagg]

yeah, it's going to be the $() bash subcommands that are the problem on windows, but we could pull them apart pretty easily.

const commitdatecmd = '$(git show -s --format=%cd {{refcmd}})' is the offending piece, used for both sincecmd and untilcmd, we could get rid of the $() around that and run them separately with gitexec(), store the output of both and then insert them back into the parent git log.

[XhmikosR]

@rvagg sounds good, can you push your suggestion on this branch and ping me?

[rvagg]

I started playing with this today but it's way more complex than I imagined! there's a lot of bash subcommand nesting going on in the original structure that's a bit awkward to pull apart. An interesting challenge though; but very low priority so no guarantees that it's going to get done any time soon.