Gitmoji: Semantic Categories & Sorting for Improved Gitmoji Navigation & Workflow

[D1no]

I love gitmoji and I we have been using them for a while (well... I kinda forced my staff...). However, it is tedious to always scan for the right gitmoji given a certain context.

Following the gitflow approach

• Manage (=master)
• Create (feature)
• Refine (hotfix)

// =============================================================================
// Mangage...
// =============================================================================
    // ...delivery
    🎉  Initial commit. - (:tada:)
    🔖  Releasing / Version tags. - (:bookmark:)
    🚀  Deploying stuff. - (:rocket:)
    🔀  Merging branches. - (:twisted_rightwards_arrows:)
    ⏪  Reverting changes. - (:rewind:)
    📝  Writing docs. - (:memo:)
    📄  Adding or updating license. - (:page_facing_up:)

    // ...value
    📈  Adding analytics or tracking code. - (:chart_with_upwards_trend:)
    🌐  Internationalization and localization. - (:globe_with_meridians:)
    💬  Updating text and literals. - (:speech_balloon:)
    ♿  Improving accessibility. - (:wheelchair:)

    // ...infrastructure
    🗃  Performing database related changes. - (:card_file_box:)
    🐳  Work about Docker. - (:whale:)

    // ...integration
    👷  Work on CI build system. - (:construction_worker:) // "Work on" instead
    💚  Fixing CI Build. - (:green_heart:)

// =============================================================================
// Create...
// =============================================================================
    // ...features
    ✨  Introducing new features. - (:sparkles:)
    🚧  Work in progress. - (:construction:)
    💥  Introducing breaking changes. - (:boom:)

    // ...changes
    💄  Updating the UI and style files. - (:lipstick:)
    🍱  Adding or updating assets. - (:bento:)
    🔥  Removing code or files. - (:fire:)
    🚚  Moving or renaming files. - (:truck:)

    // ...reliability
    🔧  Changing configuration files. - (:wrench:)
    ➕  Adding a dependency. - (:heavy_plus_sign:)
    ⬆  Upgrading dependencies. - (:arrow_up:)
    ➖  Removing a dependency. - (:heavy_minus_sign:)
    ⬇  Downgrading dependencies. - (:arrow_down:)

    // ...ideas
    💩  Writing bad code that needs to be improved. - (:hankey:)
    🍻  Writing code drunkenly. - (:beers:)

// =============================================================================
// Refine...
// =============================================================================
    // ...flaws
    🐛  Fixing a bug. - (:bug:)
    ✏  Fixing typos. - (:pencil2:)
    ✅  Adding tests. - (:white_check_mark:)
    🚨  Removing linter warnings. - (:rotating_light:)
    💡  Documenting source code. - (:bulb:)

    // ...quality
    🎨  Improving structure / format of the code. - (:art:)
    👌  Updating code due to code review changes. - (:ok_hand:)
    👽  Updating code due to external API changes. - (:alien:)
    ⚡  Improving performance. - (:zap:)
    🔨  Refactoring code. - (:hammer:)
    📦  Updating compiled files or packages. - (:package:)

    // ...stability
    🚑  Critical hotfix. - (:ambulance:)
    🔒  Fixing security issues. - (:lock:) // "Addressing" instead of "Fixing"
    🍏  Addressing iOS. - (:green_apple:) // "Addressing" instead of "Fixing"
    🤖  Addressing Android. - (:robot:)) // "Addressing" instead of "Fixing"
    🕸  Addressing Web and Browser. - (:web:) // Non-Standard Gitmoji
    🛰  Addressing Server. - (:satellite:) // Non-Standard Gitmoji

    🍎  Fixing something on macOS. - (:apple:)
    🐧  Fixing something on Linux. - (:penguin:)
    🏁  Fixing something on Windows. - (:checkered_flag:)

I am not 100% sure about the categories, but it should probably not be more than 3. This list feels, due to categorization and sorting more approachable for usual workflows (though probably not perfect) because — in many cases — emojis can simply be chained top to down.

I.e. fixing a bug on ios: 🐛📦 🍏
-> "Fixing bug by re-compiling libraries for xcode."

We work with react-native and web. We are going to create promotion material that will incorporate gitmoji as swag / print out cards.

We'll likely go with this but I want to gather feedback to see what could be improved.

Best
Dino

[carloscuesta]

Hey @D1no

I don't think we really need a categorization for Gitmojis, I think it's better to keep it simple!

[D1no]

Hey @carloscuesta, ok that is fair. My goal is to formalize the emoji use as a tag system that aligns with common workflows.

Since we use many emojis as CI triggers of certain kinds, we decided to build a development framework around our use of emojis. The full spec will release on August 23. at my talk on React Native Continues Integration Strategies in Berlin. I designed a cheat-sheet following the principle, that — though not officially released — can anyone download here:

Simply Print and Fold (you don't need staples — just stick the ends into each other).

gitmoji-triangle-A4.pdf
gitmoji-triangle-US-Letter.pdf

This can also be used as a general github cheat sheet.

Best
Dino

[carloscuesta]

Looks cool! Though I think that the paper format it's not really usable, as long as it becomes outdated really quickly

I don't think categories are necessary and your idea differs a little bit from gitmoji but I love to see things built with gitmoji 🎉 😄

[D1no]

Well as a framework, there should be hardly any breaking changes. And if so, one maybe has to run
lp -d pullprint gitmoji-triangle-A4.pdf to get up to date 😅

Cheers & nice Sunday!