Skip to content
πŸš€Emoji-Log β€” An Emoji Git commit log messages spec standard. [ πŸ“¦πŸ‘ŒπŸ›πŸ“–πŸš€βœ… ]
Branch: master
Clone or download
meyercm and ahmadawais πŸ› FIX: Remove copy/paste typo in README.md (#13)
* πŸ› FIX: Remove copy/paste typo in README.md (#12)

* πŸ“¦ NEW: Lingo
Latest commit 5ff2332 Mar 3, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
badges πŸ“¦ NEW: Badges May 5, 2018
packages/commitlint-config-emoji-log
.clTemplate.hbs
.gitignore πŸ‘Œ IMPROVE: git ignore Sep 15, 2018
.release-it.json πŸ“¦ NEW: release-it Sep 15, 2018
CHANGELOG.md
README.md πŸ› FIX: Remove copy/paste typo in README.md (#13) Mar 3, 2019
dummy.commitlintrc.js πŸ‘Œ IMPROVE: testing commit lint Sep 15, 2018
lerna.json
package-lock.json
package.json πŸ¦„ RELEASE: 0.7.0 Sep 15, 2018

README.md

EMOJI-LOG

After building hundreds of open source software I've ended up inventing a git commit log standard called EMOJI-LOG.

emoji-log


Philosophy

PHILOSOPHY

I like emoji. I like ’em a lot. Programming, code, geeks/nerds, open source, all of that is inherently dull and sometimes boring. Emoji (which is, in fact, the plural of emoji) helps me add colors and emotions to the mix. Nothing wrong if you want to attach feelings to this 2D flat text-based world of code. I found out that instead of memorizing hundreds of emoji it's better to keep the categories small and general.

  1. IMPERATIVE ↓
    • Make your Git commit messages imperative.
    • Write commit message like you're giving an order.
    • E.g., Use βœ… Add instead of ❌ Added.
    • E.g., Use βœ… Create instead of ❌ Creating.
  2. RULES ↓
    • A small number of categories β€” easy to memorize.
    • Nothing more nothing less.
    • E.g. πŸ“¦ NEW, πŸ‘Œ IMPROVE, πŸ› FIX, πŸ“– DOC, πŸš€ RELEASE, and βœ… TEST
  3. ACTIONS ↓
    • Make git commits based on actions you take.
    • Use a good editor like VSCode to commit the right files with commit messages.

Start

GETTING STARTED

Only use the following Git Commit Messages. A simple and small footprint is critical here.

  1. πŸ“¦ NEW: IMPERATIVE_MESSAGE_GOES_HERE

    Use when you add something entirely new. E.g. πŸ“¦ NEW: Add Git ignore file

  2. πŸ‘Œ IMPROVE: IMPERATIVE_MESSAGE_GOES_HERE

    Use when you improve/enhance piece of code like refactoring etc. E.g. πŸ‘Œ IMPROVE: Remote IP API Function

  3. πŸ› FIX: IMPERATIVE_MESSAGE_GOES_HERE

    Use when you fix a bug β€” need I say more? E.g. πŸ› FIX: Case converter

  4. πŸ“– DOC: IMPERATIVE_MESSAGE_GOES_HERE

    Use when you add documentation like README.md, or even inline docs. E.g. πŸ“– DOC: API Interface Tutorial

  5. πŸš€ RELEASE: IMPERATIVE_MESSAGE_GOES_HERE

    Use when you release a new version. E.g. πŸš€ RELEASE: Version 2.0.0

  6. βœ… TEST: IMPERATIVE_MESSAGE_GOES_HERE

    Use when it's related to testing. E.g. βœ… TEST: Mock User Login/Logout

β€” That's it for now. Nothing more nothing less.


More

THE WORKFLOW & MEANINGS

I'd like to share what each of these emojis mean.

  • πŸ“¦ NEW: Emoji meaning: A "package emoji" β€” which can contain new stuff.
  • πŸ‘Œ IMPROVE: Emoji meaning: An "OK Hand emoji" β€” which is meant to appreciate an improvement.
  • πŸ› FIX: Emoji meaning: A "bug emoji" β€” which means there was a bug that got fixed.
  • πŸ“– DOCS: Emoji meaning: A "book emoji" β€” which means documentation or notes just like in a book.
  • πŸš€ RELEASE: Emoji meaning: A "rocket emoji" β€” which is meant to show a new release/launch.
  • βœ… TEST: Emoji meaning: A "check emoji" β€” which says some test were run successfully.

For quick prototyping, I have made the following functions that you can add to your .bashrc/.zshrc files and use Emoji-Log quickly.

#.# Better Git Logs.
### Using EMOJI-LOG (https://github.com/ahmadawais/Emoji-Log).

# Git Commit, Add all and Push β€” in one step.
function gcap() {
    git add . && git commit -m "$*" && git push
}

# NEW.
function gnew() {
    gcap "πŸ“¦ NEW: $@"
}

# IMPROVE.
function gimp() {
    gcap "πŸ‘Œ IMPROVE: $@"
}

# FIX.
function gfix() {
    gcap "πŸ› FIX: $@"
}

# RELEASE.
function grlz() {
    gcap "πŸš€ RELEASE: $@"
}

# DOC.
function gdoc() {
    gcap "πŸ“– DOC: $@"
}

# TEST.
function gtst() {
    gcap "βœ… TEST: $@"
}

To install these functions for the fish shell, run the following commands:

function gcap; git add .; and git commit -m "$argv"; and git push; end;
function gnew; gcap "πŸ“¦ NEW: $argv"; end
function gimp; gcap "πŸ‘Œ IMPROVE: $argv"; end;
function gfix; gcap "πŸ› FIX: $argv"; end;
function grlz; gcap "πŸš€ RELEASE: $argv"; end;
function gdoc; gcap "πŸ“– DOC: $argv"; end;
function gtst; gcap "βœ… TEST: $argv"; end;
funcsave gcap
funcsave gnew
funcsave gimp
funcsave gfix
funcsave grlz
funcsave gdoc
funcsave gtst

If you prefer, you can paste these aliases directly in your ~/.gitconfig file:

# Make sure you're adding under the [alias] block.
[alias] 
  # Git Commit, Add all and Push β€” in one step.
  cap = "!f() { git add .; git commit -m \"$@\"; git push; }; f"

  # NEW.
  new = "!f() { git cap \"πŸ“¦ NEW: $@\"; }; f"
  # IMPROVE.
  imp = "!f() { git cap \"πŸ‘Œ IMPROVE: $@\"; }; f"
  # FIX.
  fix = "!f() { git cap \"πŸ› FIX: $@\"; }; f"
  # RELEASE.
  rlz = "!f() { git cap \"πŸš€ RELEASE: $@\"; }; f"
  # DOC.
  doc = "!f() { git cap \"πŸ“– DOC: $@\"; }; f"
  # TEST.
  tst = "!f() { git cap \"βœ… TEST: $@\"; }; f"

Using

USING EMOJI-LOG

Here's a list of repos that make use of Emoji-Log.


badge

EMOJI-LOG BADGE COLLECTION

If your repo uses EMOJI-LOG then you can add any of the following badges to your read me and send me a PR to list your repo here.


emoji-log

  • STYLE: Flat Square
  • MARKDOWN ↓
[![emoji-log](https://cdn.rawgit.com/ahmadawais/stuff/ca97874/emoji-log/flat.svg)](https://github.com/ahmadawais/Emoji-Log/)
  • HTML ↓
<a href="https://github.com/ahmadawais/Emoji-Log/"><img alt="emoji-log" src="https://cdn.rawgit.com/ahmadawais/stuff/ca97874/emoji-log/flat.svg" /></a>

emoji-log

  • STYLE: Flat Rounded
  • MARKDOWN ↓
[![emoji-log](https://cdn.rawgit.com/ahmadawais/stuff/ca97874/emoji-log/flat-round.svg)](https://github.com/ahmadawais/Emoji-Log/)
  • HTML ↓
<a href="https://github.com/ahmadawais/Emoji-Log/"><img alt="emoji-log" src="https://cdn.rawgit.com/ahmadawais/stuff/ca97874/emoji-log/flat-round.svg" /></a>

emoji-log

  • STYLE: Non-flat Rounded
  • MARKDOWN ↓
[![emoji-log](https://cdn.rawgit.com/ahmadawais/stuff/ca97874/emoji-log/non-flat-round.svg)](https://github.com/ahmadawais/Emoji-Log/)
  • HTML ↓
<a href="https://github.com/ahmadawais/Emoji-Log/"><img alt="emoji-log" src="https://cdn.rawgit.com/ahmadawais/stuff/ca97874/emoji-log/non-flat-round.svg" /></a>

Hello

SUPPORT OPEN SOURCE PROJECTS 🎩

If you'd like us to keep producing professional free and open source software (FOSS). Consider paying for an hour of my dev-time. We'll spend two hours on open source for each contribution. Yeah, that's right, you pay for one hour and get both of us to spend an hour as a thank you.


Thanks

LICENSE & ATTRIBUTION

MIT Β© Ahmad Awais.

Thanks to Munawar for making awesome badges for this project. This FOSS (free and open source software) project is updated and maintained with the help of excellent businesses listed below. Without the support from these amazing companies/individuals, this project would not have been possible. What/How? Read more about it β†’

Feel free to say πŸ‘‹ on Twitter @MrAhmadAwais β†’

You can’t perform that action at this time.