loading...

re: How to write a good commit message VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Short and clear, thank you for this article! I tend to use emojis for the type - it shows the type of the commit at first glance, e.g.: βž• :heavy_p...
 

Thanks for your tip!

Here is the web for other Git emoji ideas: gitmoji.carloscuesta.me/

For me, it looks too much to remember,

so I just use some emojis to keep it simple:

πŸŽ‰ :tada: initial commit πŸŽ‰

πŸš€ :rocket: [Add] when implementing a new feature

πŸ”¨ :hammer: [Fix] when fixing a bug or issue

🎨 :art: [Refactor] when refactor/improving code

🚧 :construction: [WIP]

πŸ“ :pencil: [Minor] Some small updates

 

My pleasure 😊
This is also a nice interpretation, in the end it's a matter of taste, I think.

 

It is too much to remember. I use github.com/carloscuesta/gitmoji-cli so that I don't have to remember which emoji is used for which type. It's a git commit hook, so I just do git commit, and it interactively helps me pick the appropriate emoji, write my commit message, and then drops it into my editor to make changes as needed.

If you must use an additional tool to remember your emoji meaning, I bet other too are lost for the interpretation of the emoji, once the wow effect has passed, I think words are much easier and quicker to understand :)

I almost always use both: emoji for recognizing the commit type at first glance and text for a clear and unambiguous description πŸ‘πŸ»

yes but even for the commit type, I find a word more meaningful than an emoji (and new people on the project / people reading commits without being part of the project) don't need to learn what emoji corresponds to what :).

You make using emojis sound like rocket science πŸ˜… we're talking about little pictures with clear content. A hammer is for fixing something, a scroll is for something documentation related. There really isn't much to learn πŸ€·β€β™‚οΈ

Code of Conduct Report abuse