# head: <type>(<scope>): <subject>
# - type: feat, fix, docs, style, refactor, test, chore
# - scope: can be empty (eg. if the change is a global or difficult to assign to a single component)
# - subject: start with verb (such as 'change'), 50-character line
#
# body: 72-character wrapped. This should answer:
# * Why was this change necessary?
# * How does it address the problem?
# * Are there any side effects?
#
# footer:
# - Include a link to the ticket, if any.
# - BREAKING CHANGE
#
git message规范整理
Commit Message规范
1. 标题行
type的类型为:
2. 主题内容
描述为什么修改,做了什么样的修改,以及开发思路相关
3. 页脚注释
一些备注, 通常是 BREAKING CHANGE 或修复的 bug 的链接
4. 实例
规范化
1. 设置git commit 模板
通过
git commit
进入多行编辑模式2. 使用工具进行规范化提交
安装步骤:
使用:
详情参见: https://juejin.im/post/5afc5242f265da0b7f44bee4
3. 配置强制进行检查,不通过,不予提交
参考文档