A 2 minute read written by
Marte Dybendal Gleditsch
Version control software is an essential part of modern-day software developer practices, and Git is by far the most used system. However, the amount of commits, pull requests and activity in general may be huge, and reduce the value of the git history. The Open Source project Gitmoji is a standardized emoji guide for your commit messages which enables you to assign an emoji at the beginning of commits. It even comes with an interactive client that lets you access the emojis through your command line. Although emojis are always fun, the question arises; is it just a gimmick or does it add any value?
Overview of Gitmojis: https://gitmoji.carloscuesta.me
A picture says more than words
Gitmoji was born to make it easier for developers to identify the purpose of others commits. With gitmoji others or your future self can simply look at the associated emoji and straightaway catch the intention. That in itself is a powerful feature for a developer analyzing line by line with text and code. And not to mention, the colors and joy it brings to the commit history.
A small set of gitmojis make commits easy to identify
However, some emojis are more recognizable than others and the Gitmoji guide currently consists of 66 different emojis describing different intentions, some more useful than others. The 🐛 emoji is easily recognized as a bug by most people, but will 🔥 immediately signalize that code is removed?
The learning process is an important factor with successful use of gitmoji. By selecting a small set of emojis, you and the contributors can rapidly recognize the emojis and their meanings, which is the whole idea with gitmoji in the first place. Some of the emojis are more general than others. I would recommend using those more general rather than the more detailed ones unless their usage is frequently and should be highlighted. What emojis that are selected should vary depending on technology and which stack you are working in. Frontend repositories would for example use 💄for UI changes, an emoji less relevant for backend development.
Forces you to make smaller and more specific commits
A positive outcome of using gitmoji is the fact that it forces you to think through the content and message of your commits to a larger extent. It might reduce the urge to combine completely different changes in the same commits, or even writing diffuse commit messages like
small fixes. The purpose of commit messages is to communicate context about a change to other developers working on that project, and indeed, to your future self. Gitmojis may contribute to making this history more understandable a long time after the changes were committed.
May also be used for pull request titles
Originally, gitmoji is meant for assigning emojis to the commit messages. This may be suitable for large pull requests with many commits of different nature. However, a small pull request with a defined objective may have fewer commits of similar nature. In this case, assigning gitmojis to the pull request title may be more relevant. From experience, doing both adds value.
Gitmoji will add value to your development project by simplifying code collaboration. Using a small set of emojis, suitable for your project, will make it easy for the contributors to recognize the intention of the commit. It may also contribute to better and more precise commits, and last but not least it definitely adds joy and excitement ✨💥🚑🤖.