fix: yes should be default for confirmCommit

[mauricekleine]

We would like to use cz-customizable in our company and we think it makes sense to be able to press ENTER until the end, without any extra effort, until you've created the commit. Hence, we propose to make 'yes' the default option in confirmCommit

[leonardoanalista]

Hi @mauricekleine thanks for the PR. I absolutely agree yes should be the default always. Do you think we should release this as a breaking change as we are changing the way people use this tool today? Just asking the question because we have 10K downloads a month and I am sure some people could would appreciate to know about the changes before they upgrade. What do you think?

[mauricekleine]

@leonardoanalista good point. I agree with you, this should be considered a breaking change, because I reckon if this is part of your muscle memory (pressing 'y' instead of enter), this change might be super frustrating.

[leonardoanalista]

🎉 This PR is included in version 6.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[leonardoanalista]

Great! I merged and changed the commit message to have BREAKING CHANGE in the description. This way semantic-release automatically identifies the breaking change and releases as major. Version 6.0.0 has been released as I was typing here.

[mauricekleine]

@leonardoanalista awesome, thank you!

[leonardoanalista]

No problems. If you have any further suggestions please open an issue at any time 👍