何时使用“杂务"?作为提交消息的类型? [英] When to use "chore" as type of commit message?

问题描述

语义版本控制提交消息中的chore有什么用途?其他类型，例如 feat 或 fix 很清楚，但我不知道何时使用杂项".

What is the use of chore in semantic version control commit messages? Other types like feat or fix are clear, but I don't know when to use "chore".

任何人都可以提供几个使用示例吗?

Can anyone provide a couple of examples of its use?

另一个可能不相关的问题:用于修改.gitignore之类的文件的提交消息的正确类型是什么?

Another maybe not related question: What's the proper type of messages of commits for modifying files like .gitignore?

推荐答案

您可以在"

chore :更新Grunt任务等；没有生产代码更改

chore: updating grunt tasks etc; no production code change

它用于:

• "语义提交消息"和

• 项目" fteem/git-semantic-commits ".

• "Semantic Commit Messages" and in

• the project "fteem/git-semantic-commits".

 git chore "commit-message-here" -> git commit -m 'chore: commit-message-here' 

修改.gitignore将是琐事"的一部分.

Modifying the .gitignore would be part of the "chores".

"grunt task"表示外部用户不会看到的任何内容:

"grunt task" means nothing that an external user would see:

• 实现(现有功能，不涉及修复)，
• 配置(如.gitignore或.gitattributes)，
• 内部专用方法...

• implementation (of an existing feature, which doesn't involve a fix),
• configuration (like the .gitignore or .gitattributes),
• private internal methods...

尽管 Owen S 提到

查看您链接到的业力页面 ，我怀疑grunt task可能专门引用 JavaScript的构建工具grunt .
在这种情况下，他们可能没有想到涉及实现或私有内部方法的更改，而是工具更改，配置更改以及对实际上根本不投入生产的事物的更改.
(我们的商店目前将其用于这些目的，也用于简单的重构.)

Looking at the Karma page you link to, I suspect that grunt task may refer specifically to Javascript's build tool grunt.
In which case, they probably didn't have in mind changes involving implementation or private internal methods, but rather tool changes, configuration changes, and changes to things that do not actually go into production at all.
(Our shop currently uses it for those, and also for simple refactoring.)

这篇关于何时使用“杂务"?作为提交消息的类型?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！