feat: warn on empty config

[escapedcat]

https://github.com/marionebl/commitlint/issues/107

Description

Push empty rules error to commitlint results if no rules are found.

How Has This Been Tested?

See: https://github.com/marionebl/commitlint/compare/master...escapedcat:feat/107_warn-on-empty-config?expand=1#diff-9ab1790ed00b7ca8fb5c7def7e9d2641R49

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[escapedcat]

  src/library/get-prompt.js:18:1
  ⚠  18:1  Function getPrompt has a complexity of 21.  complexity

  1 warning

Linting fails because of this. I don't think this is caused by my changes.

[escapedcat]

@commitlint/cli:   × should work with husky via commitlint -e %GIT_PARAMS% Error: Test was expected to fail, but succeeded, you should stop marking the test as failing

What is causing this? I already mentioned it in the slack channel.

[marionebl]

@commitlint/cli:   × should work with husky via commitlint -e %GIT_PARAMS% Error: Test was  expected to fail, but succeeded, you should stop marking the test as failing

What is causing this? I already mentioned it in the slack channel.

Let's skip the failing test for now. We'll remove the $GIT_PARAMS handling for good when this is in master

[marionebl]

Apart from the failing test this is ready to merge. Let's skip the test as discussed.

[byCedric]

Oh my bad, I created two separate (both different) approaches to fix the failing test here.

• https://github.com/marionebl/commitlint/pull/499
• https://github.com/marionebl/commitlint/pull/498