As a user, when I `gitmoji -c` with changes not staged, I get frustrated when I get an error after typing my message knowing I will need to type it again

Hello @carloscuesta!

As a user, when I gitmoji -c with changes not staged, I get frustrated when I get an error after typing my message knowing I will need to type it again.

Issue:

My main problem with this is that sometimes I forget to git add the changes before trying commiting, so I call gitmoji -c and happily type my commit message, and when I’m done typing, I get a non-user-friendly error saying that I had nothing to commit, the problem here is that I don’t wanna type my message again.

So my proposal would be either:

• save a cached version of what the user typed if there is an error with git, so that when I get an error, I type gitmoji -c again and the message is pre-filled, I can just press enter or I can even change it if it’s not what I want; or
• check before beginning the inquiry If there are changes to commit, and if there aren’t any changes to commit, just throw a preemptive error so I don’t have to type anything to begin with.

OS: Ubuntu 16.04.7 LTS 16.04 xenial gitmoji -v: 3.2.16 Node version: v14.15.0

Error Message:

No error, it’s just a behavior I want to change 😄

[carloscuesta]

No worries! Published 4.5.0 with this improvement 👍🏼

[vhoyer]

Oh, I guess it’s my fault for not reading the changelog… Thanks 😊