Fast and User Friendly: Our Alternative to Gitmoji

In the world of software development, it is important to document changes to projects quickly and efficiently. One way to do this is to add emojis to commit messages to quickly identify the nature of the changes. A well-known and popular tool that we like to use at Identeco is gitmoji.

A screenshot of the command `git log`. One can see three commit messages: 'πŸ’š Adopt hadolint suggestions', 'πŸš€ Pull base images on build', '⬆️  Upgrade dependencies'

But what if you’re a programmer and want to work even faster and realize the meaning of emojis more quickly in the context of Semantic Versioning? This is where our newly developed alternative comes in. It’s easier to use, with just the keyboard and no mouse, and therefore faster. Because what always bothered me when you go to the original Gitmoji website is that you always have to click in the search box first, or focus with Ctrl+K. Then you type in your search term and have to select the right Gitmoji with the mouse (or focus on the right Gitmoji with lots of Tab and then copy it with Enter). All this takes a lot of time.

Our newly developed implementation simplifies this process significantly. When you enter the page, the cursor is already activated in the search field. Once you enter the search term, you can either copy the first emoji with a simple Enter or click directly through the emojis using Tab and then copy it with Enter. This saves a lot of time in your daily workflow and a lot of switching between keyboard and mouse.

Our gitmoji alternative

Our gitmoji alternative makes it easier to document changes, supports semantic versioning, and provides additional emojis. More efficient work for programmers, easier project management. Try it out now!
Just try it

In addition, the emojis are labeled with their meaning for semantic versioning, which makes it easier to recognize the meaning. Especially for new developers, the meanings are not always clear, so this additional information can be a valuable help.

Semantic Versioning, also known as SemVer, is a convention for the version management of software. It specifies how the versions of a software should be numbered and what kind of changes are behind each version. SemVer consists of three parts: Major version, Minor version and Patch version. Each of these parts is represented by a number and separated by a period. For example: 1.4.3.

The major version represents major changes that may be incompatible with the previous version. Examples are changes to the API or removal of functions. The minor version represents new functionality, but compatible with the previous version. Examples include new features or enhancements to existing features. The patch version stands for minor changes and bug fixes that are compatible with the previous version. Examples are bug fixes or minor optimizations.

Semantic Versioning

  • v1.2.0 β†’ v1.2.1: ✏️ Fix typos and UI presentation issues
  • v1.2.0 β†’ v1.3.0: ✨ Introducing advanced search
  • v1.3.0 β†’ v2.0.0: πŸ’₯ Remove deprecated functions

Gitmoji uses this concept and combines it with emojis to more quickly identify the type of change. For example, an emoji for a major change (major version) could be a πŸ’₯ and a new feature (minor version) could be indicated by a ✨, while an emoji for a minor change like a bug fix (patch version) could be a πŸ›. In our tool, emojis are labeled with their meaning in terms of semantic versioning. This makes it possible to understand the meaning of the emojis faster than it is possible in the original implementation.

Depending on the needs of our developers, we can easily add more emoji to our gitmoji implementation. For changes related to Docker, we have already added a 🚒.

Overall, our alternative provides a faster and more user-friendly way to document changes to projects and understand the meaning of emojis faster. Give it a try and see for yourself!

Reading Time:
3 min
Published:
:
Pascua Theus

Contact an Expert

Do you have any further questions or need specific help? Write us a message or arrange a meeting directly.

Show more

  1. Verify Login Credentials to Protect against Credential-Stuffing Attacks

    Verify Login Credentials to Protect against Credential-Stuffing Attacks

    Users to Verify Their Login Credentials to Protect against Credential-Stuffing Attacks Checking credentials against leaked login information is an important safeguard to protect against credential stuffing attacks, as it helps prevent the use of stolen credentials. When users check their credentials on a platform that matches whether the data has been leaked in the past, they can determine whether their credentials may have already fallen into the hands of attackers. If so, they should change their password as soon as possible and, if necessary, consider other security measures such as enabling two-factor authentication.

    Reading Time:
    8 min
    Published:
    :
    Rene Neff
  2. Risks to Users and Operators of Online Platforms from Credential-Stuffing Attacks

    Risks to Users and Operators of Online Platforms from Credential-Stuffing Attacks

    Risks to Users of Online Platforms from Credential-Stuffing Attacks Credential stuffing attacks pose a high risk for users of online platforms. Criminals’ access to online accounts can lead to financial damage, for example when purchasing goods with stolen credit cards or by exploiting access data to paid offers. Credential-stuffing attacks also pose a risk of identity theft, as attackers may have access to personal information and documents when they access an account.

    Reading Time:
    4 min
    Published:
    :
    Rene Neff

Get to the blog