Feat: show commit msg length (closes #36)

[aichbauer]

Maybe we should add character to the message? Like

The commit message is not allowed to be longer as 72 character, but is 85 character long. Consider writing a body.

Maybe we should also add the current characters to the warning if there are not enough characters. Like

The commit message has to be at least 10 character, but is only 8 character long.

[coveralls]

Coverage remained the same at 100.0% when pulling 5f8cd43 on feat/commitMsgLength into 270d752 on master.

[JPeer264]

LGTM (just waiting for the AppVeyor CI)

[aichbauer]

I had the same Problem in another repo.

Looks like its a bug from [email protected] only on windows.

Error: EPERM: operation not permitted on npm 5.4 on windows

Downgrading to [email protected] could help?

[aichbauer]

So should we also add this to the The commit message has to be at least 10 character text? Should we add the word character or not?

[JPeer264]

This just occurs on npm@5+?

Yes, I guess adding the word characters may help some people understanding the warning.

[aichbauer]

It is a problem with [email protected] with [email protected] it should work... I faced the same problem with sgr... and it worked downgrading appveyor to [email protected]... if no version is specified, appveyor installs the latest version... in this case [email protected]...

should I downgrade the npm version in the appveyor.yml?

[coveralls]

Coverage remained the same at 100.0% when pulling 9b158dd on feat/commitMsgLength into 270d752 on master.

[JPeer264]

@aichbauer ya please downgrade, if that is really the issue 👍

[coveralls]

Coverage remained the same at 100.0% when pulling d345b6f on feat/commitMsgLength into 270d752 on master.