-
-
Save yanana/bf46d1c2a174ccff76be855767c3bbfc to your computer and use it in GitHub Desktop.
Emojiで楽しく綺麗なコミットを手に入れる(改)
This file contains hidden or 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 ==== | |
| # 🎨 :art: improving format/structure of the code | |
| # 🔧 :wrench: infra/tooling | |
| # 🔎 :mag: when adding or improving the code for monitoring | |
| # 🐛 :bug: when fixing bug | |
| # 👍 :+1: improved feature | |
| # ✨ :sparkles: when adding a partial feature | |
| # 🎉 :tada: big feature | |
| # 🔥 :fire: when removing code or files | |
| # 💚 :green_heart: when fixing the CI builds | |
| # 👕 :shirt: when removing linter warnings | |
| # 🚀 :rocket: when improving performance | |
| # ⬆️ :up: when upgrading dependencies | |
| # ⬇️ :down: when downgrading dependencies | |
| # 👮 :cop: when improving security | |
| # ==== Format ==== | |
| # :emoji: Subject | |
| # | |
| # Commit body... | |
| # ==== Commit message Rules ==== | |
| # 1. Separate subject from body with a blank line | |
| # 2. Limit the subject line to 72 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 | |
| # 8. When only changing documentation, include [ci skip] in the commit description | |
| # How to Write a Git Commit Message http://chris.beams.io/posts/git-commit/ | |
| # for http://memo.goodpatch.co/2016/07/beautiful-commits-with-emojis/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment