longer description how to new line？

[GHJayce]

Provide a longer description of the change: (press enter to skip)

Pressing the Enter key will proceed to the next question, not a line break.

Have you encountered a similar situation with me, is there a solution?

[wangjiancn]

\n

[GHJayce]

thanks. It works, If this example is the same, I still find it difficult to write long descriptions.

[in-in]

I also wonder how to break the string for the description field while typing Symbol \ and \n didn't work for me

The \ symbol works in the terminal, but not in the cz-cli prompt

⇒ echo foo\ 
> bar           
foobar

[realduolaf]

Symbol \ and \n didn't work in my terminal, too.

I find the issue #398 . But do you have any plans to provide a more convenient way?

[PaulRBerg]

+1 for this.

A solution would be to just skip the long description prompt and then do git commit --amend to open the vim editor.

[akakoori]

+1 This is somewhat annoying , and I think it departs from the aim of this tool, which is to make committing easy.

[hydra1983]

+1

[tvvignesh]

Bump. This is difficult to handle. \n did not work for me as well. Can you help or let us know if there is any fallback till this is taken up? Thanks.

[RichieMerchant]

I use git commit -e and edit the message before the commit fires.

[CanRau]

another option is

git commit -m "first line (subject)" -m "body" -m "more body (new paragraph)" -m "footer"

git commit -e is also very helpful, but defining multiple -m messages you don't even need to wait for your editor to open the file etc 😉

[ImagineBoom]

git cz -e

[geoffreyvanwyk]

Based on #398, if you change "input" to "editor" on line 126 in node_modules/cz-conventional-changelog/engine.js for the 'body' variable, when prompted for the body, you can press "Enter" and your editor will open wherein you can enter the body.

Therefore, the issue is actually with repository https://github.com/conventional-changelog/conventional-changelog. This issue can be closed.