commitizen / commitizen/cz-cli

commitizen produces empty commit message after answering prompts

Aperta
#967 3 commenti 1 reazione 0 assegnatari Vedi su GitHub
Lingua principale
JavaScript
Stelle
17.5k
Fork
566
Merge medio
8h 16m
PR unite (30g)
1

Descrizione

### Description

We set up `cz` as a husky pre-commit hook but when we go through the prompts via `git commit` it produces an empty commit message in `vim`.

These commands were executed to set it up:

```
npm install --save-dev commitizen
npx commitizen init cz-conventional-changelog --save-dev --save-exact
npx husky-init && npm install
```

Our `.husky/prepare-commit-msg`:

```
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

echo '[husky] Running commitizen for prepare-commit-msg hook...'
exec < /dev/tty && npx cz --hook || true
```

### Steps to reproduce

1. Execute `git commit`.
2. Answer the cz prompts.
3. A vim editor is opened.

### Current behavior

The vim editor has an empty commit message and commitizen errors out due to an empty commit message.

### Desired behavior

commitizen produces a commit message using information entered in prompts.

### Screenshots

```
git commit
[husky] Running commitizen for prepare-commit-msg hook...
cz-cli@4.3.0, cz-customizable@7.0.0

All lines except first will be wrapped after 100 characters.
? Select the type of change that you're committing: chore: Changes that don't modify src or test files
?
Denote the SCOPE of this change (optional): empty
? Write a SHORT, IMPERATIVE description of the change:
cz message prompt tweak
? Provide a LONGER description of the change (optional). Use "|" to break new line:
false
? List any ISSUES CLOSED by this change (optional). E.g.: #31, #34:

str.match is not a function
Aborting commit due to empty commit message.
```

![image](https://user-images.githubusercontent.com/179807/218177263-80a59267-dff1-452a-b8a4-ace39f0ae9a6.png)

### Environment

cz-cli@4.3.0
cz-customizable@7.0.0

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start with the .husky/prepare-commit-msg hook and reproduce the issue by running git commit, answering the commitizen prompts, and observing the Vim editor and str.match error. Trace how the prompted values are passed into the commit message; done means the entered prompt data produces a non-empty commit message without the error.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
git, javascript, node.js
Ambito
cli, tooling
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
30/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.