git 何时使用“杂项”作为提交消息的类型？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/26944762/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
When to use "chore" as type of commit message?
提问by Alireza Mirian
What is the use of chorein semantic version control commit messages? Other types like feator fixare clear, but I don't know when to use "chore".
什么是使用chore在语义版本控制提交信息？其他类型如feat或fix很清楚，但我不知道何时使用“杂务”。
Can anyone provide a couple of examples of its use?
谁能提供几个使用它的例子？
Another maybe not related question: What's the proper type of messages of commits for modifying files like .gitignore?
另一个可能不相关的问题：用于修改文件的提交消息的正确类型是.gitignore什么？
回答by VonC
You can see a short definition in "Git Commit Msg":
你可以在“ Git Commit Msg”中看到一个简短的定义：
chore: updating grunt tasks etc; no production code change
chore：更新 grunt 任务等；没有生产代码更改
It is used in:
它用于：
- "Semantic Commit Messages" and in
the project "
fteem/git-semantic-commits".git chore "commit-message-here" -> git commit -m 'chore: commit-message-here'
- “语义提交消息”和
项目“
fteem/git-semantic-commits”。git chore "commit-message-here" -> git commit -m 'chore: commit-message-here'
Modifying the .gitignorewould be part of the "chores".
修改.gitignore将是“杂务”的一部分。
"grunt task" means nothing that an external user would see:
" grunt task" 表示外部用户不会看到任何内容：
- implementation (of an existing feature, which doesn't involve a fix),
- configuration (like the
.gitignoreor.gitattributes), - private internal methods...
- 实现（现有功能，不涉及修复），
- 配置（如
.gitignore或.gitattributes）， - 私有内部方法...
Although Owen Smentions in the comments:
Looking at the Karma page you link to, I suspect that
grunt taskmay refer specifically to Javascript's build toolgrunt.
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.)
查看您链接到的Karma 页面，我怀疑
grunt task可能专门指的是Javascript 的构建工具grunt。
在这种情况下，他们可能没有想到涉及实现或私有内部方法的更改，而是工具更改、配置更改以及对根本没有实际投入生产的事物的更改。
（我们的商店目前将它用于那些，也用于简单的重构。）
