"Please add your rules to your `commitlint.config.js`" when using @commitlint/config-conventional

Expected Behavior

commitlint to utilize the node module @commitlint/config-conventional when performing git commit and after having created a commitlint.config.js file that extends config-conventional: echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js

Current Behavior

husky > commit-msg (node v12.16.1)
⧗   input: refactor: remove old files, add dev files
✖   Please add rules to your `commitlint.config.js`
    - Getting started guide: https://git.io/fhHij
    - Example config: https://git.io/fhHip [empty-rules]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

husky > commit-msg hook failed (add --no-verify to bypass)

Affected packages

• cli

Steps to Reproduce (for bugs)

Follow the instructions here: https://commitlint.js.org/#/guides-local-setup

Don’t add any additional rules to commitlint.config.js and attempt a git commit.

Your Environment

Windows 10 Pro 19041

Executable	Version
commitlint --version	9.0.1
git --version	2.27.0.windows.1
node --version	12.16.1

[Zirak]

Tried reproducing without success:

$ npm i @commitlint/cli @commitlint/config-conventional

# from original comment
$ echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js

# sample commit message from original comment
$ echo 'refactor: remove old files, add dev files' | npx commitlint -V
⧗   input: refactor: remove old files, add dev files
✔   found 0 problems, 0 warnings

$ npx commitlint --version
@commitlint/cli@16.0.2

[guijiangheng]

@escapedcat You might create a .commitlint.config.js instead of commitlint.config.js, you might use a wrong filename just like me.