Git最佳做法提交日志 [英] Git best practice commit logs

查看:116
本文介绍了Git最佳做法提交日志的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

一个愚蠢的问题,但我认为它有它的地位在这个。

Kind of a stupid question, but I think it have its place on SO.

我看到很多提交日志在开源项目,看起来像这样;

I am seeing a lot of commit logs on opensource projects that looks like this;

feat(something): Some description here
fix(something): Some other description
chore(...): ...

等等..

我确定有一些智能工具解析这种提交日志的新风格,也可能是一个作弊书。但是,我无法找出这种风格的名称。
我错过了什么?哪里有工具,文档在哪里?

I am sure there is some smart tools that parses this new style of committing logs, and probably a cheatsheet as well. But I am having trouble finding out what this style is called. What am I missing? Where is the tools, and where is the docs?

推荐答案

我发现了一些重复模式@ https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y ,还有一个插件叫grunt-使用这种模式的常规更改日志。

I found some of the repeating pattern @ https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y and there is a plugin to grunt called grunt-conventional-changelog that uses this pattern.

看起来或多或少像AngularJS现象。角色一直是我最近的主要焦点,所以这可能是我最近几个星期以来一直在绊脚石。

Looks more or less like an AngularJS phenomen. Angular have been my main focus lately, so thats probably how I have been stumbling on this the last weeks..

这篇关于Git最佳做法提交日志的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆