Just a quick post this week as I’ve not had the time I’d hoped to look at the coding exercise I wanted to blog about – mainly because I was getting so fed up with my Windows laptop feeling like it was about to fall apart I decided to pull the trigger on an M1 MacBook Air and I’ve been busy setting up my environment on there.
So, what I’m going to talk about is how fun Gitmoji are! What are Gitmoji? Well, they’re basically emoji. Nothing special or new, but the idea of using them in Git commits is as an easily identifiable tag that explains what the commit is. Is it refactoring code, redoing some of the front end HTML or CSS or even something simple as updating some comments or documentation? There’s a recommended emoji for all those scenarios and you can check them at this handy cheat sheet on gitmoji.dev.
We’ve been using them in our commits at Laser Red for a few weeks now and they’ve not only helped make it clearer what we’re committing but they’ve also made me in particular think about how chunky my commits are – ideally I like to use only one or two emoji per commit so I’ve really started keeping them lean and to the point, committing little and often to the repo.
It’s something I’ve already started applying to my own github repo’s so it’ll be something you’ll start to see popping up on my own projects that I’ll be discussing here in the future.
If you don’t already tag your commits with Gitmoji, give them a try and, if you do, let me know how you find them in the comments!