Created
December 25, 2016 01:18
-
-
Save dorayakikun/7d44c19a07c92341edb0f3b62c77a7cc to your computer and use it in GitHub Desktop.
Git Commit Messages
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# ==== Emojis ==== | |
# π¦ :package: New release | |
# β¨ :sparkles: when adding a new feature | |
# β»οΈ :recycle: when improving the format/structure of the code | |
# π :rocket: when improving performance | |
# π± :non-potable_water: when plugging memory leaks | |
# π :closed_book: when writing docs | |
# π :bug: when fixing a bug | |
# π₯ :fire: when removing codes or files | |
# π :green_heart: when fixing the CI build | |
# β :white_check_mark: when adding tests | |
# π :lock: when dealing with security | |
# π :shirt: when removing linter warnings | |
# β¬οΈ :arrow_up: when upgrading dependencies | |
# β¬οΈ :arrow_down: when downgrading dependencies | |
# ==== 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/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment