Fabrizio Destro
Fabrizio Destro
I tried your solution and is not working, the same exception as before. From what I understand from issue #123 it should be possible to use commitlint from any directory...
Which version of Ubuntu are you using? I tried with Ubuntu 18.04 on a VM created with vagrant and I am having the same problem. ``` /usr/local/lib/node_modules/@commitlint/cli/lib/cli.js:113 throw err; ^...
I tried with node version `10.15.3` and npm version `6.4.1` and now it's working.
IMO it would be much more simply working with this library if it would be possible to include it as a dependency, hosted on some maven repository. This would resolve...
The workaround does not work in my case, spotless still fails with `java.lang.NullPointerException`. Maybe this can be useful, when I follow the workaround and add back all files I get...
I know the solution is to generate the file beforehand, but I am not comfortable with the idea to have the possibility to generate a project that compiles but fails...
I think this `--strict` flag could be useful, especially in this scenario where I don't want the project to be generated if the file is missing.
I managed to get GitHub renders a file without extension as a Markdown file by adding a vim modelines at the top. ``` ``` To accomplish this I followed the...