commitizen / commitizen/cz-cli

Running Commitizen on `git commit` with cli script

Abierto
#714 0 comentarios 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
17.5k
Forks
566
Merge medio
8 h 16 min
PR fusionados (30 d)
1

Descripción

I am trying to combine these two sections from docs:
[Running Commitizen on `git commit`](https://github.com/commitizen/cz-cli#optional-running-commitizen-on-git-commit) and [Commitizen for multi-repo projects](https://github.com/commitizen/cz-cli#commitizen-for-multi-repo-projects).

Repository to reproduce: https://github.com/arvigeus/commit
(configuration is in [packages/git-config](https://github.com/arvigeus/commit/tree/master/packages/git-config), cli is in [packages/git-config/conventional-commit.js](https://github.com/arvigeus/commit/blob/master/packages/git-config/conventional-commit.js), nothing special)

When I add a new file and try to commit it, I get the following error:

```sh
$ git commit
husky > pre-commit (node v10.19.0)
✔ Preparing...
✔ Running tasks...
✔ Applying modifications...
✔ Cleaning up...
husky > prepare-commit-msg (node v10.19.0)
/media/data/Workspace/arvigeus/commit/node_modules/commitizen/node_modules/cz-conventional-changelog/index.js:10
defaultType: process.env.CZ_TYPE || config.defaultType,
^

TypeError: Cannot read property 'defaultType' of undefined
at Object. (/media/data/Workspace/arvigeus/commit/node_modules/commitizen/node_modules/cz-conventional-changelog/index.js:10:46)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at getPrompter (/media/data/Workspace/arvigeus/commit/node_modules/commitizen/dist/commitizen/adapter.js:1391:41)
at gitCz (/media/data/Workspace/arvigeus/commit/node_modules/commitizen/dist/cli/strategies/git-cz.js:62:18)
husky > commit-msg (node v10.19.0)
/media/data/Workspace/arvigeus/commit/node_modules/@commitlint/cli/lib/cli.js:124
throw err;
^

TypeError: Cannot read property 'length' of null
at exports.default (/media/data/Workspace/arvigeus/commit/node_modules/@commitlint/rules/lib/header-max-length.js:10:143)
at results.filter.map.entry (/media/data/Workspace/arvigeus/commit/node_modules/@commitlint/lint/lib/index.js:151:17)
at Array.map ()
at Object. (/media/data/Workspace/arvigeus/commit/node_modules/@commitlint/lint/lib/index.js:131:7)
at process._tickCallback (internal/process/next_tick.js:68:7)
husky > commit-msg hook failed (add --no-verify to bypass)
```

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza con las secciones de documentación enlazadas y el repositorio proporcionado, especialmente packages/git-config/conventional-commit.js, y luego reproduce el fallo con git commit. Se considera terminado cuando la configuración combinada de varios repositorios y git commit se ejecuta sin el error de defaultType indefinido ni el posterior fallo de commitlint.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
git, javascript, node.js
Área
cli, tooling
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.