Emojis can make messages playful, fun, exciting.
Your documentation and commit logs should be none of this.
Keep your emojis the fuck out of them.

They are not there for the fun. They are there for categorization, not just textual, but also visually in order to increase performance and decrease error rates.

Now get back to work before I fire you.

@petergriffin At least [Fix], [Feat], [Chore], etc are easily searchable. If someone cannot differentiate these visually of they are placed in a single column, emojis won't help them either. And in documentation they absolutely make no sense at all.

Sadly, you're right :(

I do not want to believe this but I do

Well if people notice there are cringe emojis in your doc and tell you about it, it means someone read it.

If you do not hear about it by anybody, either everyone enjoys it or nobody actually reads the docs...

git commit -m "🤡 Make this package great again 🤡"

I have never "luckily" seen an emoji commit message in a work environment... But if I did it would kinda throw me off... :(

public class 📕
{
public void ✏️ (string 📑)
{
}
}

@kwilliams might be fun using though.

string 📑 = "Ten thousand ways to die";
new 📕().✏️(📑);

Maybe they are added as a cry for help

You can write C++ in hieroglyphics..

I have never used emojis in real work commits, but I wanna.

Who said this shouldn't be playful/fun?

@nanobot Work should definitely be fun. But personally I think the fun comes from interesting tasks, friendly collegues, a good company culture, and easy to use documentation; not pseudo-engaging emojis.