Emoji log is a new way to write your Git Commit Messages. I like emoji. I like ’em a lot. Programming, code, geeks, nerds, open source, all of that is inherently dull and sometimes boring. I improve that by using Emoji.
I also am a big fan of the Don’t Repeat Yourself (DRY) philosophy and believe writing better Git commit messages—ones that are contextual enough to serve as a changelog for your open source software—is an important component of DRY.
One of the many workflows I’ve written is Emoji-Log, a straightforward, open source Git commit log standard. It improves the developer experience (DX) by using emoji to create better Git commit messages. For more check out my article on OpenSource.com
Instead of memorizing hundreds of emoji, I’ve learned it’s better to keep the categories small and general. Here’s the philosophy that guides writing commit messages with Emoji-Log:
- IMPERATIVE: Make your Git commit messages imperative. Write commit message like you’re giving an order.
— Use ✅ Add instead of ❌ Added.
— Use ✅ Create instead of ❌ Creating.
- RULES: A small number of categories are easy to memorize. Nothing more, nothing less. There are only six types of Emoji log. One should only use these six types and nothing else. Which are
→ 📦 NEW: [Git Commit Message goes here]
→ 👌 IMPROVE: [Git Commit Message goes here]
→ 🐛 FIX: [Git Commit Message goes here]
→ 📖 DOC: [Git Commit Message goes here]
→ 🚀 RELEASE: [Git Commit Message goes here]
→ ✅ TEST: [Git Commit Message goes here]
- ACTIONS: Make Git commits based on actions you take. Use a good editor like VSCode to commit the right files with commit messages.
Takeaway my professional opinion on open-source, developer relations, growing your business with family, and everything in between! Delivered to your inbox a couple of times every year. I'm even funny at times. I hate spam — pinky-promise!
👨💻👩💻 168,174 Developers Already Subscribed