guilhiz / react-boilerplate Goto Github PK

📝 Description

This issue aims to address a bug that occurs when committing using Commitzen. Currently, when a user runs git commit without providing a commit message, Commitzen prompts the user to enter a message using its interface. However, after the user confirms the message, the default text editor is opened for them to edit the message again, resulting in unnecessary time loss and confusion for users who prefer to use Commitzen for their commit messages.

🚀 Steps to Reproduce

1. Run git add to stage changes
2. Run git commit without providing a message to use Commitzen
3. Use the Commitzen interface to write and confirm the commit message
4. Observe that the default text editor opens, even though the commit message has already been confirmed using Commitzen.

ezgif.com-gif-maker.mp4

👀 Expected Behavior

After confirming the commit message using the Commitzen interface, the commit should be made without opening the default text editor. This would improve the user experience by eliminating unnecessary steps and reducing confusion.

🤔 Previous Attempts

I attempted to solve this issue by checking the Commitzen documentation and trying different configurations in my Git hooks, but none of them seem to work. Usually, changing the code of the Git hooks only caused more problems, such as Commitzen running twice or lint-staged not working. From what I found, the solution adopted by most people was simply to create a script or an alias to avoid using git commit. I am considering adopting one of these ideas, but I decided to open this issue to try my luck.

📌 Task List

• Modify Commitzen or git hook prepape-commit-msg to enable committing without opening the default text editor after confirming the commit message using the Commitzen interface.