Hacker News Reader

Comment by fbnlsr | Hacker News Reader

Wait, I thought the goal of it is not to write emojis per se but rather use the shortcodes. That way, it's readable even when emojis cannot be rendered and it even makes search easier. So a typical commit message would read like that:

`:bug: Fix login modal`

It doesn't break anything and when interpreted (github, gitlab, gitkraken, etc...) it displays a nice looking emoji.

View on HN

This is how Slack and I believe Discord handle emojis as well. Interestingly even if you copy and paste a unicode emoji it's translated into a code.

Doesn't 'fix' already mean there was a bug, that was 'fix'-ed?

A better example would be:

`:lipstick: Revamp login modal`

> Doesn't 'fix' already mean there was a bug, that was 'fix'-ed?

Read this: https://stackoverflow.com/questions/3580013/should-i-use-pas...

TLDR from the Git repo: Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behavior.

People have different opinions on what tense to use, but the one that scales better would be in imperative mood. See example here: https://github.com/facebook/react

I don't think this answers the question?

How come? As I understand the comment, the user is questioning the tense of "fix" and I'm providing a reason and an example as to why someone would use imperative mood in their commit message.

Edit: Nevermind. I must have been tired yesterday. User wasn't questioning the tense, but pointing out that the part of the message "fix" making the :emoji: redundant.

Agreed. I think this actually argues in favor of using a [fix] tag over [bug].

Reply on news.ycombinator.com