fix(scripts/commit-msg): actually forward arguments to commitlint 😞

- Fixes use case of actually passing `--edit $1` for example
- Also fixes passing a custom config via `--config`

Author: jrolfs

src/scripts/__tests__/__snapshots__/commit-msg.js.snap

@@ -4,8 +4,8 @@ exports[`commit-msg adds env flag with HUSKY_GIT_PARAMS when available 1`] = `co
 
 exports[`commit-msg calls @commitlint/cli with default args 1`] = `commitlint --config ./src/config/commitlint.config.js`;
 
-exports[`commit-msg does not use built-in config with --config 1`] = `commitlint`;
+exports[`commit-msg does not use built-in config with --config 1`] = `commitlint --config ./custom-config.js`;
 
 exports[`commit-msg does not use built-in config with commitlint.config.js file 1`] = `commitlint`;
 
-exports[`commit-msg forwards args 1`] = `commitlint --config ./src/config/commitlint.config.js`;
+exports[`commit-msg forwards args 1`] = `commitlint --config ./src/config/commitlint.config.js --edit .git/COMMIT_EDITMSG`;

src/scripts/__tests__/commit-msg.js

@@ -57,7 +57,7 @@ cases(
       hasFile: filename => filename === 'commitlint.config.js',
     },
     'forwards args': {
-      args: ['--verbose'],
+      args: ['--edit', '.git/COMMIT_EDITMSG'],
     },
     'adds env flag with HUSKY_GIT_PARAMS when available': {
       env: {HUSKY_GIT_PARAMS: 'husky-git-params'},

src/scripts/commit-msg.js

@@ -21,7 +21,7 @@ const config = useBuiltinConfig
 
 const result = spawn.sync(
   resolveBin('@commitlint/cli', {executable: 'commitlint'}),
-  [...env, ...config],
+  [...env, ...config, ...args],
   {
     stdio: 'inherit',
   },