DEV Community

loading...

Selecting the Right Emotion for Your Commit

jessekphillips profile image Jesse Phillips Updated on ・1 min read

This idea that your emotions can tell a story is new to me, but it could be that emoji encompasses much more than emotions now.

I've been utilizing gitmoji for some time now. And many on the team are liking what it is doing to their commits, even if I push on some things which seem too hard to break up.

I wanted to explain a couple of these icons though.

✨ - New features
♻️ - Refactoring
💥 - Breaking changes
🏗️ - Architecture changes

One of the rules is that you can't commit with more than one. And since the commit is reviewed to identify that is the only thing you're doing.

What had me stumble for a bit was how I decided between an architecture or breaking changes and here is what I came up with:

🏗️ - ♻️ 💥
💥 - ✨ 💥

They are both breaking changes. One is when your refacing went too far and changed an important api and the other is when it happens while adding a new feature.

This makes me think that a good migration plan would entail


♻️
And
🔥 - Remove code

The idea being a new api is provided before the old one is removed.

Discussion (3)

Collapse
jessekphillips profile image
Jesse Phillips Author

Even having just written this. I could see using 🏗 for commits that remove depreciation. But that is mainly because in my case I have code removal which is a breaking change.

Collapse
jwollner5 profile image
John 'BBQ' Wollner

I'd be happy if my team described what they changed and leave out there emotional context lol!

Collapse
nabbisen profile image
Heddi Nabbisen

Nice and interesting approach :)
It's new to me ✨
It helps me a lot 💥

Forem Open with the Forem app