.commit_template

# ==== Emojis ====
# 🎨  :art: when improving the format/structure of the code
# 🔧  :wrench: when improving infrastructure/tooling
# 🚀  :rocket: when improving performance
# 🚱  :non-potable_water: when plugging memory leaks
# 📝  :memo: when writing docs
# 🐛  :bug: when fixing a bug
# 💚  :green_heart: when fixing the CI build
# ✅  :white_check_mark: when adding tests
# 👮  :cop: when dealing with security
# ⬆️  :arrow_up: when upgrading dependencies
# ⬇️  :arrow_down: when downgrading dependencies
# 👕  :shirt: when removing linter warnings
# 👍  :+1: when improving functions
# ✨  :sparkles: when adding partial functions
# 🎉  :tada: when adding big functions
# ♻️  :recycle: when refactoring code
# 🔥  :fire: when removing code or files

# ==== Format ====
# :emoji: Subject
#
# Commit body...

# ==== The Seven Rules ====
# 1. Separate subject from body with a blank line
# 2. Limit the subject line to 50 characters
# 3. Capitalize the subject line
# 4. Do not end the subject line with a period
# 5. Use the imperative mood in the subject line
# 6. Wrap the body at 72 characters
# 7. Use the body to explain what and why vs. how
#
# How to Write a Git Commit Message http://chris.beams.io/posts/git-commit/