执行 git commit 时使用 emoji 为本次提交打上一个 "标签", 使得此次 commit 的主要工作得以凸现，也能够使得其在整个提交历史中易于区分与查找。

git commit 时，提交信息遵循以下格式：

:emoji1: :emoji2: 不超过 50 个字的摘要，首字母大写，使用祈使语气，句末不要加句号

提交信息主体

引用相关 issue 或 PR 编号 <#110>

初次提交示例：

git commit -m ":tada: Initialize Repo"

• gitmoji
• emoji-cheat-sheet
• styleguide-git-commit-message
• atom git commit messages guide
• An emoji guide for your commit messages
• 程序员提交代码的 emoji 指南——原来表情文字不能乱用
• Ant Design 更新日志 emoji 规范

• A Note About Git Commit Messages
• How to write a Git Commit Message (2014)
• how to write a good git commit message
• 5 Useful Tips For A Better Commit Message
• Udacity Git Commit Message Style Guide
• How to commit a change with both “message” and “description” from the command line?

• Capitalize the .<subject>

• Do not end the first line with a period.

• Total characters of the first line MUST be Less than or Equal to 50 characters Long.

• Use the present tense ("Add feature" not "Added feature").

• Use the imperative mood ("Move cursor to..." not "Moves cursor to...").

• Use to identify what type of changes introduced in this commit; Allowed keywords:

  <type>
  

  <type>
  

  • An Emoji(see below for list of Suggested Emojis)
  • Or a Text:
    • feat: 用户的新功能(或 something 表情符号)
    • fix: bug fix for the user (or emoji)
    • docs: 更改文档(或表情符号)
    • style: 格式，缺少分号等; 没有生产代码更改(或表情符号)
    • refactor: 重构生产代码，例如重命名变量(或表情符号)
    • test: 添加缺少的测试，重构测试; 没有生产代码更改(或表情符号)
    • chore: 更新粗活等; 没有生产代码更改

• Reference issues this commit is related to with the status of that Issue; Ex. , or or .Issue #27``Ref T27``Ref T27, T56``Fixes T8
• Supported issue tracker status keywords:
  • Fixes
  • Fixed
  • Closes
  • Closed
  • Resolves
  • Resolved
  • Ref
  • Issue
  • Issues

- 提交(CLI) : 这是一个漂亮的 CLI 工具，可以帮助标准化基于此文档的提交消息，感谢@jakeasmith。

- gitMoji (Firefox & Chrome 扩展) : 使用 emoji 增强提交功能，感谢@louisgrasset

- 代码表情符号 : Mozilla 的代码表情符号用表情符号加密你的信息，以获取乐趣和利润

- 基于表情符号的图表 : 基于表情符号的数据轴承订阅更新图表(WebPush VAPID)

• Use the present tense ("Add feature" not "Added feature")
• Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
• Limit the first line to 72 characters or less
• Reference issues and pull requests liberally after the first line
• When only changing documentation, include in the commit title[ci skip]
• Consider starting the commit message with an applicable emoji:
  • 🎨 :art: when improving the format/structure of the code
  • 🐎 :racehorse: when improving performance
  • 🚱 :non-potable_water: when plugging memory leaks
  • 📝 :memo: when writing docs
  • 🐧 :penguin: when fixing something on Linux
  • 🍎 :apple: when fixing something on macOS
  • 🏁 :checkered_flag: when fixing something on Windows
  • 🐛 :bug: when fixing a bug
  • 🔥 :fire: when removing code or files
  • 💚 :green_heart: when fixing the CI build
  • ✅ :white_check_mark: when adding tests
  • 🔒 :lock: when dealing with security
  • ⬆️ :arrow_up: when upgrading dependencies
  • ⬇️ :arrow_down: when downgrading dependencies
  • 👕 :shirt: when removing linter warnings

• 🐞 Bug 修复
• 💄 样式更新/less 变量更新
• 🆕 新增特性
• 🔥 极其值得关注的新增特性
• 🇺🇸🇨🇳🇬🇧 国际化改动，注意这里直接用对应国家/地区的旗帜。
• 📖 📝 文档或网站改进
• ✅ 新增或更新测试用例
• 🛎 更新警告/提示信息
• ⌨️ ♿ 可访问性增强
• 🗑 废弃或移除
• 🛠 重构或工具链优化
• ⚡️ 性能提升

Continue with a longer description a.k.a. message body:

• Add a blank line after the summary line, then write as much as you want. 在摘要行后添加一个空行，然后随心所欲地写。
• Use up to 72 characters per line for typical text for word wrap. 对于自动换行的典型文本，每行最多使用 72 个字符。
• Use as many characters as needed for atypical text, such as URLs, terminal output, formatted messages, etc. 对非典型文本使用尽可能多的字符，例如 URL、终端输出、格式化消息等。
• Include any kind of notes, links, examples, etc. as you want. 包括任何类型的注释、链接、示例等。如你所愿。

We recommend these summary keywords because they use imperative mood, present tense, active voice, and are verbs:

我们推荐以下摘要关键字，因为它们使用命令式语气、现在时态、主动语态，并且是动词：

• Add: Create a capability e.g. feature, test, dependency. 创建一个功能，例如特性，测试，依赖。
• Drop: Delete a capability e.g. feature, test, dependency. 删除功能，例如功能，测试，依赖。
• Fix: Fix an issue e.g. bug, typo, accident, misstatement. 修复一个问题，例如 bug，输入错误，事故，错误陈述。
• Bump: Increase the version of something e.g. a dependency. 增加某事物的版本，例如依赖关系
• Make: Change the build process, or tools, or infrastructure. 改变构建过程，或工具，或基础设施。
• Start: Begin doing something; e.g. enable a toggle, feature flag, etc. 开始做一些事情; 例如，启用一个切换，功能标志等。
• Stop: End doing something; e.g. disable a toggle, feature flag, etc. 结束做某事，例如禁用切换，功能标志等。
• Optimize: A change that MUST be just about performance, e.g. speed up code.一个改变，必须只是性能，例如加速代码。
• Document: A change that MUST be only in the documentation, e.g. help files.只能在文档中进行的更改，例如帮助文件。
• Refactor: A change that MUST be just a refactoring patch一个改变，必须只是一个重构补丁
• Reformat: A change that MUST be just a formatting path, e.g. change spaces.一个必须只是格式化路径的更改，例如，更改空格。
• Rearrange: A change that MUST be just an arranging patch, e.g. change layout. 一个必须只是安排补丁的更改，例如更改布局。
• Redraw: A change that MUST be just a drawing patch, e.g. change a graphic, image, icon, etc. 一个改变，必须只是一个绘图补丁，例如改变图形，图像，图标等。
• Reword: A change that MUST be just a wording patch, e.g. change a comment, label, doc, etc. 一个修改，必须只是一个措辞补丁，例如改变一个评论，标签，文档等。
• Revise: A change that MUST be just a revising patch e.g. a change, an alteration, a correction, etc. 一个修改，必须是一个修改补丁，例如一个变化，一个修改，一个更正等。
• Refit/Refresh/Renew/Reload: A change that MUST be just a patch e.g. update test data, API keys, etc. 一个必须是补丁的更改，例如更新测试数据、 API 密钥等。